I am working on an application where I need to reboot individual nodes in the cluster as quickly as possible. In order to do so, I am first putting the node into standby mode and then shutting down Pacemaker. This works well in most cases - except when the node I am shutting down is the DC and has a Master resources that need to be promoted on another node. In this case, the Pacemaker shutdown seems to be delayed until both the local resources are stopped AND the remote resources are promoted and/or started. This causes an unacceptable delay in the reboot of the node.
Am I correctly interpreting why the Pacemaker shutdown is taking so long? Is there any way to fix this? The idea solution would seem to be to force the DC to another node before putting the node into standby mode, but there doesn’t seem to be a mechanism to do so. Is there another way to deal with this? To summarize: I basically need to cleanly shutdown the resources on the node and exit the cluster as quickly as possible so that I can reboot the node and rejoin the cluster with minimal delay. Any suggestions are appreciated! Dennis LaCroix _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/developers ClusterLabs home: https://www.clusterlabs.org/
