[ClusterLabs] Stopped node detection.

Ken Gaillot kgaillot at redhat.com
Fri Oct 16 10:27:44 EDT 2015

On 10/15/2015 03:55 PM, Vallevand, Mark K wrote:
> Ubuntu 12.04 LTS
> pacemaker 1.1.10
> cman 3.1.7
> corosync 1.4.6
> If my cluster has no resources, it seems like it takes 20s for a stopped node to be detected.  Is the value really 20s and is it a parameter that can be adjusted?

The corosync token timeout is the main factor, so check your corosync.conf.

Pacemaker will then try to fence the node (if it was stopped uncleanly),
so that will take some time depending on what fencing you're using.

Generally this takes much less than 20s, but maybe you have a longer
timeout configured, or fencing is not working, or something like that.
The logs should have some clues, post them if you can't find it.

More information about the Users mailing list