<div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div><br>Thank you for your response! This means that there shoudn't be long "sleep" in ocf script.</div><div>If my service takes 10 minite from service starting to healthcheck normally, then what shoud I do? </div><div>Thank you very much!</div><div> </div><div>> Hi,</div><div>> If I remember correctly, any pending actions from a previous transition<br>> must be completed before a new transition can be calculated. Otherwise,<br>> there's the possibility that the pending action could change the state<br>> in a way that makes the second transition's decisions harmful.</div><div>> Theoretically (and ideally), pacemaker could figure out whether some of<br>> the actions in the second transition would be needed regardless of<br>> whether the pending actions succeeded or failed, but in practice, that<br>> would be difficult to implement (and possibly take more time to<br>> calculate than is desirable in a recovery situation).</div><div> </div><div>> On Fri, 2017-10-27 at 23:54 +0800, lkxjtu wrote:</div><div><br>> I have two clone resources in my corosync/pacemaker cluster. They are<br>> fm_mgt and logserver. Both of their RA is ocf. fm_mgt takes 1 minute<br>> to start the<br>> service(calling ocf start function for 1 minite). Configured as<br>> below：<br>> # 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<br>> When I kill fm_mgt service on one node，pacemaker will immediately<br>> recover it after monitor failed. This looks perfectly normal. But in<br>> this 1 minite<br>> of fm_mgt starting, if I kill logserver service on any node, the<br>> monitor will catch the fail normally too，but pacemaker will not<br>> restart it<br>> immediately but waiting for fm_mgt starting finished. After fm_mgt<br>> starting finished, pacemaker begin restarting logserver. It seems<br>> that there are<br>> some dependency between pacemaker resource.<br>> # crm status<br>> Last updated: Thu Oct 26 06:40:24 2017 Last change: Thu Oct<br>> 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<br>> with quorum<br>> 3 nodes and 6 resources configured<br>> Online: [ 192.168.2.177 192.168.2.178 192.168.2.179 ]<br>> Full list of resources:<br>> 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 ]<br>> I am confusing very much. Is there something wrong configure?Thank<br>> you very much!<br>> James<br>> best regards</div><blockquote style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;" id="isReplyContent"><div style="color: rgb(0, 0, 0); line-height: 1.7; font-family: Arial; font-size: 14px;"><p> </p><br><br><span title="neteasefooter"><div id="netease_mail_footer"><div style="padding: 10px 5px; color: rgb(119, 119, 119); line-height: 22px; font-size: 17px; border-top-color: rgb(204, 204, 204); border-top-width: 1px; border-top-style: solid;"><a style="color: rgb(51, 102, 255); text-decoration: none;" href="http://you.163.com/item/detail?id=1183001&from=web_gg_mail_jiaobiao_7" target="_blank">【网易自营】好吃到爆！鲜香弹滑加热即食，经典13香/麻辣小龙虾仅75元3斤>> </a>
</div></div></span></div><br><br><span title="neteasefooter"><div id="netease_mail_footer"><div style="padding: 10px 5px; color: rgb(119, 119, 119); line-height: 22px; font-size: 17px; border-top-color: rgb(204, 204, 204); border-top-width: 1px; border-top-style: solid;"><a style="color: rgb(51, 102, 255); text-decoration: none;" href="http://you.163.com/item/detail?id=1183001&from=web_gg_mail_jiaobiao_7" target="_blank">【网易自营】好吃到爆！鲜香弹滑加热即食，经典13香/麻辣小龙虾仅75元3斤>> </a>
</div></div></span></blockquote></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>