<div style="line-height:1.6;font-size:16px;font-family:'苹方','微软雅黑','sans-serif';">Does anyone know this question?<br><br>best regards<font style="font-size:16px;"><br><br></font><br><font style="color:rgb(49,53,59);"><font style="font-size:16px;">发自网易邮箱手机版</font></font><br><br></div><div class="ne-quoted"><blockquote id="ntes-andriodmail-quote" style="margin:0px !important;padding:0px !important;border: none !important;"><div class="J-reply" style="background-color:#f2f2f2;color:black;padding-top:6px;padding-bottom:6px;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;margin-top:45px;margin-bottom:20px;">
<div style="font-size:14px;line-height:1.5;word-break:break-all;margin-left:10px;margin-right:10px">在<span class="mail-date">2017年10月25日 23:10</span>，<a class="mail-to" style="text-decoration:none;color:#2a97ff;" href="mailto:lkxjtu@163.com">lkxjtu</a> 写道：</div>
</div><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div>My problem is about the pacemaker. For example,the pacemaker cluster has two resources, both of them resource agent are ocf. One of resource is starting(calling ocf start function), such as needing for 1 minutes, then in this 1 minutes, if another resource monitor failed, pacemaker will not immediately call stop/start method to restart it but waiting the first resource to starting complete. After the first resource start completely, the second resource begin restarting.</div><div> </div><div>My cluster version: corosync 2.3.4 pacemaker 1.1.13</div><div> </div><div>Configure as:</div><div># crm configure show<br>node 168002177: 192.168.2.177<br>node 168002178: 192.168.2.178<br>node 168002179: 192.168.2.179<br>primitive fm_mgt fm_mgt \<br> op monitor interval=20s timeout=120s \<br> op stop interval=0 timeout=120s on-fail=restart \<br> op start interval=0 timeout=120s on-fail=restart \<br> meta target-role=Started<br>primitive logserver logserver \<br> op monitor interval=20s timeout=120s \<br> op stop interval=0 timeout=120s on-fail=restart \<br> op start interval=0 timeout=120s on-fail=restart \<br> meta target-role=Started<br>clone fm_mgt_replica fm_mgt<br>clone logserver_replica logserver<br>property cib-bootstrap-options: \<br> have-watchdog=false \<br> dc-version=1.1.13-10.el7-44eb2dd \<br> cluster-infrastructure=corosync \<br> stonith-enabled=false \<br> start-failure-is-fatal=false</div><div> </div><div>When I kill fm_mgt service on 177 node, pacemaker will stop and start it immediately after firts monitor failed. But at this time, I kill a logserver service, pacemaker will not restart it after monitor failed, but waiting fm_mgt recovery completely.There are 48 seconds between logserver monitor failed and stop/start action.</div><div> </div><div># crm status<br>Last updated: Thu Oct 26 06:40:24 2017 Last change: Thu Oct 26 06:36:33 2017 by root via crm_resource on 192.168.2.177<br>Stack: corosync<br>Current DC: 192.168.2.179 (version 1.1.13-10.el7-44eb2dd) - partition with quorum<br>3 nodes and 6 resources configured</div><div>Online: [ 192.168.2.177 192.168.2.178 192.168.2.179 ]</div><div>Full list of resources:</div><div> Clone Set: logserver_replica [logserver]<br> logserver (ocf::heartbeat:logserver): FAILED 192.168.2.177<br> Started: [ 192.168.2.178 192.168.2.179 ]<br> Clone Set: fm_mgt_replica [fm_mgt]<br> Started: [ 192.168.2.178 192.168.2.179 ]<br> Stopped: [ 192.168.2.177 ]</div><div> </div><div>I am confusing very much. Is there something wrong configure?Thank you very much!</div></div><br><br><span title="neteasefooter"><div id="netease_mail_footer"><div style="border-top:#CCC 1px solid;padding:10px 5px;font-size:17px;color:#777;line-height:22px"><a href="http://you.163.com/item/detail?id=1165011&from=web_gg_mail_jiaobiao_9" target="_blank" style="color:#3366FF;text-decoration:none">【网易自营|30天无忧退货】仅售同款价1/4！MUJI制造商“2017秋冬舒适家居拖鞋系列”限时仅34.9元>> </a>
</div></div></span></blockquote></div>