Hi, On Wed, Jan 23, 2013 at 5:21 AM, Brian J. Murrell <br...@interlinx.bc.ca> wrote: > OK. So you have a corosync cluster of nodes with pacemaker managing > resources on them, including (of course) STONITH. > > What's the best/proper way to shut down a node, say, for maintenance > such that pacemaker doesn't go trying to "fix" that situation and > STONITHing it to try to bring it back up, etc.? > > Currently my practice for STONITH is to have it reboot. Maybe it's a > better practice to have STONITH configured to just power a node down and > not try to power it back up for this exact reason? > > Any other suggestions welcome.
I usually put the node in standby, which means it can no longer run any resources on it. Both Pacemaker and Corosync continue to run, node provides quorum. For global cluster maintenance, such as when upgrading to a major software version, maintenance-mode is needed. HTH, Dan > > Cheers, > b. > > > _______________________________________________ > 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 > -- Dan Frincu CCNA, RHCE _______________________________________________ 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
