I’ve heard from the guys at MySQL that the configuration of Heartbeat
communication paths in ha.cf seems to be confusing to
some. So, here’s our best practice summary:
- Never configure fewer than two communication paths. And I mean, never. Never. If you do, that’s an accident (read: split brain) waiting to happen.
- On the device that you run your DRBD replication over, if it
uses a direct back-to-back connection to the peer node (like it
should), configure a
bcastlink. Simple and easy to configure, and since you’re not sharing that link with anything other than DRBD replication, those broadcast packets won’t harm or …