On 2013-06-27T16:52:02, Dejan Muhamedagic <deja...@fastmail.fm> wrote:
> > I don't want the cluster stack to start on boot, so I disable
> > pacemaker/corosync. However, I do want the node to power back on so that
> > I can log into it when the alarms go off. Yes, I could log into the good
> > node, manually unfence/boot it and then log in, but this adds minutes to
> > the MTTR that I would realllly like to avoid.
> Certainly it adds a bit of time, but only to the node's MTTR,
> not the cluster's MTTR. Anyway, if pacemaker can turn off the
> node, then a short script can also turn it on.
sbd has gained a mechanism that allows the rebooting node to see if it
was fenced, and only then to not start the cluster stack.
I wonder if something similar could be adapted to other fencing
mechanisms?
(It is somewhat similar to corosync's new two node quorum handling, I
guess.)
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Pacemaker mailing list: Pacemaker@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
