<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>Hi,</div>
<div><br>
</div>
<div>We have a 2-node active/standby PGSQL/DRBD Cluster with STONITH and we put one node in standby</div>
<div>Then shutdown pacemaker on this standby node (service pacemaker stop), wait some sec, then doing the same</div>
<div>With corosync (service corosync stop), again wait some seconds and always have a look at crm_mon –r on the active node.</div>
<div><br>
</div>
<div>After that, the standby nodes status should be OFFLINE (standby). Then we can safely reboot or shutdown this node.</div>
<div><br>
</div>
<div>When ist rebootet, we first start DRBD and let it sync completly – then restart corosync (wich autostarts pacemaker) with</div>
<div>Service corosync start. After some moments it will become "standby" again in the cluster and you can</div>
<div>Put it back online with crm node online <nodename>.</div>
<div><br>
</div>
<div>This works very well and we dont experience any crm hang on the active node like we did when we missed to stop pacemaker and then corosync</div>
<div>Before reboot.</div>
<div><br>
</div>
<div>Also you can put everything in maintenance-mode=true, but then even on the active node PGSQL isnt monitored (restarted if it shuts down), therefore</div>
<div>We only use maintenance if we really do manual steps to PG or updating the cluster software.</div>
<div><br>
</div>
<div>Greets from Berlin,</div>
<div><br>
</div>
<div>Martin</div>
<div>
<div style="font-family: Verdana; font-size: 11px; "><br>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">Von: </span>Dan Frincu <<a href="mailto:df.cluster@gmail.com">df.cluster@gmail.com</a>><br>
<span style="font-weight:bold">Antworten an: </span>The Pacemaker cluster resource manager <<a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>
<span style="font-weight:bold">Datum: </span>Wednesday, January 23, 2013 9:32 AM<br>
<span style="font-weight:bold">An: </span>The Pacemaker cluster resource manager <<a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>
<span style="font-weight:bold">Betreff: </span>Re: [Pacemaker] best/proper way to shut down a node for service<br>
</div>
<div><br>
</div>
<div>
<div>
<div>Hi,</div>
<div><br>
</div>
<div>On Wed, Jan 23, 2013 at 5:21 AM, Brian J. Murrell <<a href="mailto:brian@interlinx.bc.ca">brian@interlinx.bc.ca</a>> wrote:</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>OK. So you have a corosync cluster of nodes with pacemaker managing</div>
<div>resources on them, including (of course) STONITH.</div>
<div><br>
</div>
<div>What's the best/proper way to shut down a node, say, for maintenance</div>
<div>such that pacemaker doesn't go trying to "fix" that situation and</div>
<div>STONITHing it to try to bring it back up, etc.?</div>
<div><br>
</div>
<div>Currently my practice for STONITH is to have it reboot. Maybe it's a</div>
<div>better practice to have STONITH configured to just power a node down and</div>
<div>not try to power it back up for this exact reason?</div>
<div><br>
</div>
<div>Any other suggestions welcome.</div>
</blockquote>
<div><br>
</div>
<div>I usually put the node in standby, which means it can no longer run</div>
<div>any resources on it. Both Pacemaker and Corosync continue to run, node</div>
<div>provides quorum.</div>
<div><br>
</div>
<div>For global cluster maintenance, such as when upgrading to a major</div>
<div>software version, maintenance-mode is needed.</div>
<div><br>
</div>
<div>HTH,</div>
<div>Dan</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div><br>
</div>
<div>Cheers,</div>
<div>b.</div>
<div><br>
</div>
<div><br>
</div>
<div>_______________________________________________</div>
<div>Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a></div>
<div><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></div>
<div><br>
</div>
<div>Project Home: <a href="http://www.clusterlabs.org">http://www.clusterlabs.org</a></div>
<div>Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">
http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a></div>
<div>Bugs: <a href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a></div>
<div><br>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>-- </div>
<div>Dan Frincu</div>
<div>CCNA, RHCE</div>
<div><br>
</div>
<div>_______________________________________________</div>
<div>Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a></div>
<div><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></div>
<div><br>
</div>
<div>Project Home: <a href="http://www.clusterlabs.org">http://www.clusterlabs.org</a></div>
<div>Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">
http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a></div>
<div>Bugs: <a href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a></div>
<div><br>
</div>
</div>
</div>
</span>
</body>
</html>