So on avg how long it took for the AWS api call to transfer the IP to standby HA Proxy? I am wondering if it makes to go with just auto scale and define minimum 1 server.
Thanks Mir On Nov 18, 2011, at 4:26 AM, Mariano Guezuraga wrote: > On 11/17/2011 10:55 PM, Mir Islam wrote: >> Hi Guys, I am wondering how people are solving the problem of HAProxy >> becoming SPOF. I am using HAproxy in Amazon cloud for SSL stick session and >> load balancing, but best solution I could come up with for making HAProxy HA >> is by having another exact instance as hot standby. Then monitor the active >> one periodically and if it goes down, move the elastic IP associated with >> HAP1 to HAP2. Is there some other way folks are solving this issue? >> Remember, on Amazon cloud instances they do not have any public IP >> associated with the actual interface. So can't create virtual interface/ip >> and move it around like in traditional "heart beat" type of systems. >> >> Thanks >> Mir > Hi, > > I'm doing exactly the same. I set up an heartbeat 2 node cluster > (active/passive), defined 2 custom ocf resources (the elastic ip and the > haproxy daemon) and grouped them to act together. The most tricky part for me > was the heartbeat monitoring function because AWS API calls are really slow > and tend to time out. > Anyway, haproxy is running nicely, so far we are getting ~300 r/s >
