[Pacemaker] Master/Slave failover during reboot

Lars Marowsky-Bree lmb at suse.de
Tue Jul 21 08:59:55 EDT 2009

On 2009-07-20T15:27:23, Eliot Gable <egable at broadvox.com> wrote:

> I have a resource that is configured as a Master/Slave resource. If I
> kill a resource it is dependent on, it properly fails over to the
> other node. However, if I reboot the master node, it does not fail
> over. What I see is that the master node switches to UNCLEAN -
> Offline, the master resource stops running (crm_mon shows only the
> slave node running) and then it just sits there until the master node
> finishes booting. Once the rebooted node re-joins the cluster, it
> figures out which is master/slave and one of them gets promoted. The
> entire time, the partition says it has quorum. This is Pacemaker
> 1.0.4.

Nodes in "Unclean - offline" state should be fenced. Since you make no
allusion to fencing/STONITH occuring, I wonder if you have fencing


Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

More information about the Pacemaker mailing list