Timeline for How does StackOverflow achieve fault tolerance for it's HAProxy instances?
Current License: CC BY-SA 2.5
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2011 at 20:25 | comment | added | Warner | The IPAddr script does an ARP broadcast to update the ARP tables after bringing the alias up. Might vary slightly if you use hb 2.x. | |
| Jan 31, 2011 at 18:18 | comment | added | Kyle Brandt | I can't remember the VIP implementation of heartbeat -- I would ask that as a question on SF proper. I think the IP probably just has the MAC address of the secondary server after a failover and hosts arp tables and mac address tables on the switch are updated accordingly but not sure. | |
| Jan 31, 2011 at 18:12 | comment | added | Kyle Brandt | Updated the question. Yup, all of StackOverflow, SF, SO, and the rest of the StackExchange network goes through a single haproxy instance. CPU usage on that machine average less than 1% and never really goes above 6%. The only exception is chat which is still hosted out of OR. | |
| Jan 31, 2011 at 18:08 | comment | added | Matthew | Thanks for the quick response. Wow so 100% of the traffic for so.com is going to a single HAProxy? Just confirming. Also please see this part of my question 'Does client traffic get sent to a single shared IP address (the "virtual") and through the magic of changing the mac address associated with the IP address, traffic goes to one of the HAProxy’s until that box fails or is taken down?' Thanks! | |
| Jan 31, 2011 at 18:06 | history | answered | Kyle Brandt | CC BY-SA 2.5 |