[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Plan to add sandbox branch

How often are nodes updating themselves? Are they only updating their main proxy server or each other in a “multicast” fashion? How about if one of the nodes crash before sending back an update? Are you locking a session to a specific backend host, keep it tracked on the proxy/front end server and if so, for how long?

When I read your message, in particular the STATUS info statement, this plan of yours looked to me like how a regular load balancer product works, and if that is the intent, how different from and/or how integrated to ATS is this going to be?


On 2018/11/27 11:23:25, Jim Jagielski <j...@xxxxxxxxxxx> wrote: 
> In the coming week or so, I will be committing my load balance,> 
> load determination and discovery work to a sandbox trunk. Many> 
> people have asked for more info, so here we go.> 
> Basically, this new feature uses nanomsg (nng) to implement the> 
> SURVEY protocol between workers (nodes) and the front end server.> 
> The proxy server will send out MEMBERSHIP and STATUS surveys, that> 
> nodes can respond to; thus new nodes can automagically add themselves> 
> as they come up as well as remove themselves when they restart or> 
> shutdown via MEMBERSHIP. STATUS can be used to provide real-time> 
> load on each node, which will be sent via a __packed__ struct,> 
> ala NTP and other common usage patterns, in which 32bit fields are> 
> converted from endian-ness to network and back. That STATUS info can> 
> be used for "intelligent" load balancing and will provide some> 
> typical server metrics such as memory, # of cpus, etc...> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature