Hi, we see there is a new feature of HAProxy, peer and share table (sticky-table). This peer feature can be used to have in synch stick cookie so if one haproxy goes down the other can take over connections ? There is some HAProxy native feature to have HAProxy nodes configuration in synch automatically or we have to rely on external tools like rsync manually or as we do on LVS a cron job executing a script to synch configuration ?
What is your choice ? For the connection limitation, you speak of frontend and per backand server minconn / maxconn ? it isn't right to divide by n (n=numero ov HAProxy) established total and per server connection ? also if this is not perfect we'll have at most always (n * maxconn). Also... I know that a major pros of L7 load balancing is to manage centrally all phase of the communication (sticky, balancing, etc. ), but in Hybrid Cloud thinking... is not right to can controll the connection up to a certain point and so using some mechanism as L4 load balancer (as LVS) to put in direct communication clients and final servers. At least for communications not rely on sticky (persistent) session, one can alleviate periodic extraordinary high connection rate redirecting connection for some services (L7 acl) in a Public Cloud wihout weigh down our Private Cloud infrastructure ? Probably there is some other way... We do not see at the moment... -----Original Message----- From: Thierry FOURNIER [mailto:[email protected]] Sent: giovedì 9 luglio 2015 14.51 To: mlist Cc: '[email protected]' Subject: Re: Load Balancing the Load Balancer On Thu, 9 Jul 2015 11:08:58 +0000 mlist <[email protected]> wrote: > We have a question about Load Balancing the load balancer... We have as now 2 > LVS load balancer in active / passive configuration with keepalived. > We want to introduce L7 load balancer (HAProxy) in active / active > configuration, so we have not only HA configuration but also load balanced > configuration of load balancer. We think we can do that using the two active > / passive LVS machine to load balancing request on 2 HAProxy machine, using > correctly persistence (LVS) and stickiness (HAProxy) so application / session > behave as expected. We do not found such solution on the Internet, do you > think this is a bad design ? Hi, this is the classic design, but make sure that the both haproxy configruation are the same (mainly with the stick cookie name and values). You must known that its not really possible to limit the amount of connexions to your servers because the first haproxy don't known the current connexions of the second haproxy. Thierry -- Il messaggio e' stato analizzato alla ricerca di virus o contenuti pericolosi da MailScanner, ed e' risultato non infetto.
