[ClusterLabs] pacemaker daemon shutdown time with lost remote node

[Radoslaw Garbacz]

Hi,

I have a question regarding pacemaker daemon shutdown
procedure/configuration.

In my case, when a remote node is lost pacemaker needs exactly 10minutes to
shutdown, during which there is nothing logged.
So my questions:
1. What is pacemaker doing at this time?
2. How to make it shorter?


Changed Pacemaker Configuration:
- cluster-delay
- dc-deadtime


Pacemaker Logs:
Apr 28 17:38:08 [17689] ip-10-41-177-183 pacemakerd:   notice:
crm_signal_dispatch:     Caught 'Terminated' signal | 15 (invoking handler)
Apr 28 17:38:08 [17689] ip-10-41-177-183 pacemakerd:   notice:
pcmk_shutdown_worker:    Shutting down Pacemaker
Apr 28 17:38:08 [17689] ip-10-41-177-183 pacemakerd:   notice:
stop_child:      Stopping crmd | sent signal 15 to process 17698
Apr 28 17:48:07 [17695] ip-10-41-177-183       lrmd:     info:
cancel_recurring_action: Cancelling ocf operation
monitor_head_monitor_191000
Apr 28 17:48:07 [17695] ip-10-41-177-183       lrmd:     info:
log_execute:     executing - rsc:monitor_head action:stop call_id:130
[...]
Apr 28 17:48:07 [17689] ip-10-41-177-183 pacemakerd:     info: main:
Exiting pacemakerd
Apr 28 17:48:07 [17689] ip-10-41-177-183 pacemakerd:     info:
crm_xml_cleanup: Cleaning up memory from libxml2


Pacemaker built from github: 1.16


Help greatly appreciated.

-- 
Best Regards,

Radoslaw Garbacz
XtremeData Incorporated
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20170428/57b5cbca/attachment-0002.html>