Yeah, keepalived handles the gratuitous arp on failover, it works nicely. I do miss the admin tools for pacemaker though. I'm AFK, but I'll write up a full explanation of our HA setup when I'm back at a PC.
Cheers, Nathan On Thu, Aug 27, 2015, 6:11 PM Shawn Heisey <hapr...@elyograg.org> wrote: > On 8/27/2015 6:52 PM, Nathan Williams wrote: > > There's a sysctl for that, net.ipv4.ip_nonlocal_bind. > > Interesting. That's one I had never seen before. I would assume that > the OS does this intelligently so that when the IP address *does* > suddenly appear at a later time, the application works seamlessly. > That's something I will have to test. > > I might need to rethink my redundancy design with this new bit of > knowledge. I have seen a number of incidents where pacemaker froze and > I had no idea there was a problem until I did maintenance on the standby > server (either rebooting it or stopping pacemaker) and the online host > didn't notice it going down. Everything kept working, but the systems > were in a state where no failover would have occurred in the event of a > failure. I bet keepalived is a lot more stable than pacemaker. > > Thanks, > Shawn > > >
