[Pacemaker] Pull the plug on one node, the resource doesn't promote the other node to master

[David Vossel]

----- Original Message -----
> From: "Matteo Bignotti" <mbignotti at switchvox.com>
> To: pacemaker at oss.clusterlabs.org
> Sent: Friday, July 20, 2012 4:01:26 PM
> Subject: [Pacemaker] Pull the plug on one node, the resource doesn't promote the other node to master
> 
> Hi guys,
> 
> I am having trouble understanding why this happens:
> 
> I have this cluster with 2 nodes, when I put one node in standby or
> crash the resource, it correctly promotes on the second machine as
> master.
> But if I UNPLUG the first machine from the network, the resource
> won't
> promote the other one to master.
> 
> I am using corosync/pacemaker
> 
> why is that?

Are you using stonith?  If node1 disappears, pacemaker has to have some sort of guarantee from a fencing device that it is in fact gone before the promotion happens.

This situation (unplugging node) differs from standby and the rsc crash because pacemaker still knows the state of node1 with after the standby/rsc crash.  If the state of node1 can't be verified (unplugged from network), it needs to be fenced before the cluster can continue.

If you are still having trouble, upload a crm_report and we'll have a look.

-- Vossel

> thanks
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started:
> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>