Is 'hash-type consistent' the way to go using hash algorithm? Map-based sounds pretty good as well?
Consistent: "In order to get the same distribution on multiple load balancers, it is important that all servers have the same IDs." Something like this? Balance source hash-type map-based /E -----Original Message----- From: Baptiste [mailto:bed...@gmail.com] Sent: den 7 november 2011 13:58 To: Erik Torlen Cc: vivek.ma...@gmail.com; David Birdsong; haproxy@formilux.org Subject: Re: Autoscaling in haproxy with persistence sessions On Mon, Nov 7, 2011 at 10:05 PM, Erik Torlen <erik.tor...@apicasystem.com> wrote: > What would you recommend if we wanted to have all our three haproxy instances > loadbalance in the same way. > And still make use of persistence when the client is using one of the haproxy > instances? > > E.g Having the client come to the same backend on both haproxy srv1, srv2 and > srv3. > > Could we make use of some hash-algorithm to achieve this? Balancing on source > ip? > The hash algorithm based on source IP looks interesting, persistence will be lost on each reload and adapted to the farm size. Worst case, the stick table + peers to synchronise + clear table on reload... But there might be undesirable side effects: if clear table is not done synchronously, then new entries will be replicated... cheers
