[ClusterLabs] Establishing Timeouts
eric.robinson at psmnv.com
Mon Oct 10 00:51:49 EDT 2016
I have about a dozen corosync+pacemaker clusters and I am just now getting around to understanding timeouts.
Most of my corosync.conf files look something like this:
If I understand this correctly, this means the node will wait 50 seconds (5000ms x 10) before deciding that a cluster reconfig is necessary (perhaps after a link failure). Is that correct?
I'm trying to understand how this works together with my bonded NIC's arp_interval settings. I normally set arp_interval=1000. My question is, how many arp losses are required before the bonding driver decides to failover to the other link? If arp_interval=1000, how many times does the driver send an arp and fail to receive a reply before it decides that the link is dead?
I think I need to know this so I can set my corosync.conf settings correctly to avoid "false positive" cluster failovers. In other words, if there is a link or switch failure, I want to make sure that the cluster allows plenty of time for link communication to recover before deciding that a node has actually died.
More information about the Users