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

Dejan Muhamedagic dejanmm at fastmail.fm
Mon Aug 17 22:58:38 UTC 2009


Hi,

On Mon, Aug 17, 2009 at 04:18:34PM -0600, hj lee wrote:
> Hi,
> 
> I defined stonith:ssh, they are running in both machines as a clone. How is

How do you expect ssh to work if you pull the power plug from the
target node?

> the stonith related to promoting standby? When the Pacemaker detects master
> node was gone in cluster, then why doesn't Pacemaker promote the standby?

In case of such an event, when a node disappears without saying
goodbye, the other node has to make sure that the node which left
is down and not only unreachable, that's where fencing comes in.

Thanks,

Dejan

> Thanks very much
> 
> On Mon, Aug 17, 2009 at 4:00 PM, Dejan Muhamedagic <dejanmm at fastmail.fm>wrote:
> 
> >
> > >
> > > 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?
> >
> > You probably didn't define fencing (stonith).
> >
> > Thanks,
> >
> > Dejan
> >
> >

> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker





More information about the Pacemaker mailing list