Thanks for the good input Tait. This would be a code mod but, maybe it would be possible to have different mgmt ports for each process. Maybe baseport+N where N is the process number. I like the IPVS option but keeping it all within HAProxy seems nicer.
This definitely gives me some cool stuff to prototype over the weekend! Peter. The real goal I am interested in is running HAProxy on virtual machines, or in the cloud, where I can provision a load balancer on a multi-cpu VM with HAPtroxy tuned with enough processes to handle a specific work flow. Before this information, I was thinking that this would be limited to only VMs with a single CPU On Fri, Feb 1, 2013 at 10:26 AM, Tait Clarridge <[email protected]> wrote: > > > Peter Mellquist <[email protected]> > 1 February, 2013 12:48 PM > Excellent, just what I was looking for! > > Peter. > > > Just remember that the admin socket will not work as expected with this as > it round robins between all the running processes. You would have to size > any specific ACLs that deal with session rate or maxconn accordingly or > your limits will be too high. > > You could also investigate installing an IPVS load balancer (keepalived) > sending to multiple haproxy processes spawned with different loopback IPs. >
<<compose-unknown-contact.jpg>>
