Thank very much for the reply.<br>
<br>
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 default), <br>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.<br>
<br>
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.<br>
<br>
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 no-quorum-policy ignore.<br>
<br>
Here are my new questions:<br>
How does stonith detect the node was actually down? Doesn't it get this
info from the cluster stack? Does it have its own mechanism like
pinging the other nodes? Can stonith:external/ipmi detect the node is down? Which type of stonith has this ability?<br><br>Always thank you very much<br>hj<br><br><div class="gmail_quote">On Mon, Aug 17, 2009 at 4:58 PM, Dejan Muhamedagic <span dir="ltr"><<a href="mailto:dejanmm@fastmail.fm">dejanmm@fastmail.fm</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
<div class="im"><br>
><br>
> I defined stonith:ssh, they are running in both machines as a clone. How is<br>
<br>
</div>How do you expect ssh to work if you pull the power plug from the<br>
target node?<br>
<div class="im"><br>
> the stonith related to promoting standby? When the Pacemaker detects master<br>
> node was gone in cluster, then why doesn't Pacemaker promote the standby?<br>
<br>
</div>In case of such an event, when a node disappears without saying<br>
goodbye, the other node has to make sure that the node which left<br>
is down and not only unreachable, that's where fencing comes in.<br><div class="im"><br>
><br>
> On Mon, Aug 17, 2009 at 4:00 PM, Dejan Muhamedagic <<a href="mailto:dejanmm@fastmail.fm">dejanmm@fastmail.fm</a>>wrote:<br>
><br>
> ><br>
> > ><br>
> > > I am very simple Master/Slave in RHEL 5.3 with pacemaker 1.0.4 and<br>
> > heartbea<br>
> > > 2.99. I unplugged the power cable at the master machine, and I expected<br>
> > the<br>
> > > slave becomes master. But the slave stays at slave state. Is this correct<br>
> > > behavior or a bug? How does Pacemaker (or heartbeat) handle this kind of<br>
> > > sudden power off?<br>
> ><br>
> > You probably didn't define fencing (stonith).<br>
> ><br>
> > Thanks,<br>
> ><br>
> > Dejan<br>
</div></blockquote></div><br>