On 06/29/2017 01:38 PM, Ludovic Vaugeois-Pepin wrote: > On Thu, Jun 29, 2017 at 7:27 PM, Ken Gaillot <kgail...@redhat.com> wrote: >> On 06/29/2017 04:42 AM, philipp.achmuel...@arz.at wrote: >>> Hi, >>> >>> In order to reboot a Clusternode i would like to set the node to standby >>> first, so a clean takeover for running resources can take in place. >>> Is there a default way i can set in pacemaker, or do i have to setup my >>> own systemd implementation? >>> >>> thank you! >>> regards >>> ------------------------ >>> env: >>> Pacemaker 1.1.15 >>> SLES 12.2 >> >> If a node cleanly shuts down or reboots, pacemaker will move all >> resources off it before it exits, so that should happen as you're >> describing, without needing an explicit standby. > > This makes me wonder about timeouts. Specifically OS/systemd timeouts. > Say the node being shut down or rebooted holds a resource as a master, > and it takes a while for the demote to complete, say 100 seconds (less > than the demote timeout of 120s in this hypothetical scenario). Will > the OS/systemd wait until pacemaker exits cleanly on a regular CentOS > or Debian?
Yes. The pacemaker systemd unit file uses TimeoutStopSec=30min. > > >> Explicitly doing standby first would be useful mainly if you want to >> manually check the results of the takeover before proceeding with the >> reboot, and/or if you want the node to come back in standby mode next >> time it joins. _______________________________________________ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org