[Pacemaker] Slave does not get become Master after unplugging power cable at master

hj lee kerdosa at gmail.com
Tue Aug 18 23:31:16 EDT 2009

Thank very much for the reply.

I tested it both stonith-enabled and no-quorum-policy. As Dejan pointed,
this is related to stonith-enabled. With stonith-enabled true (which is
if I kill the master node, the slave stays as a slave, it seems expecting
something from stonith. With stonith-enabled false, the slave was promoted
to master.

The no-quorum-policy controls the behavior when the quorum is not enough.
With no-quorum-policy stop, when one of two nodes dies, the resources in the
other node get stopped. With no-quorum-poolicy ignore, when one of two nodes
dies, nothing happens. If master die, the slave stays as a slave. If slave
dies, the master stays as a master.

By the way during the test, no-quorum-policy works only in openais stack.
With heartbeat stack, there is no difference between no-quorum-policy stop
and ignore. It seems the heartbeat stack always behavior as

Here are my new questions:
How does stonith detect the node was gone or died? Doesn't it get this info
from the cluster stack? Does it have its own mechanism like pinging the
other nodes?

Always thank you very much

On Tue, Aug 18, 2009 at 5:38 AM, Diego Remolina <
diego.remolina at physics.gatech.edu> wrote:

> Do you have an entry for:
> no-quorum-policy="ignore"
> Here is how mine looks for a 2 node master/slave drbd fileserver cluster:
> property $id="cib-bootstrap-options" \
>        dc-version="1.0.4-6dede86d6105786af3a5321ccf66b44b6914f0aa" \
>        cluster-infrastructure="openais" \
>        expected-quorum-votes="2" \
>        no-quorum-policy="ignore" \
>        last-lrm-refresh="1250006912"
> On a two node cluster, if one node goes down, there is no quorum, so the
> resources will not be migrated. You need to have this entry so that one node
> can operate on its own. This was happening to my 2 node cluster, I would
> shutdown one node and the second one would not get promoted to master, that
> was until I added the no-quorum-policy=ignore entry.
> HTH,
> Diego
> hj lee wrote:
>>  Hi,
>> I am very simple Master/Slave in RHEL 5.3 with pacemaker 1.0.4 and
>> heartbea 2.99. I unplugged the power cable at the master machine, and I
>> expected the slave becomes master. But the slave stays at slave state. Is
>> this correct behavior or a bug? How does Pacemaker (or heartbeat) handle
>> this kind of sudden power off?
>> Thanks in advance
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20090818/d20b2d9d/attachment-0001.html>

More information about the Pacemaker mailing list