[Pacemaker] About specifications of on-fail="block".
renayama19661014 at ybb.ne.jp
renayama19661014 at ybb.ne.jp
Mon Aug 9 02:49:36 UTC 2010
Hi,
Let me confirm it about specifications of on-fail="block".
I constituted the following cluster.
============
Last updated: Mon Aug 9 11:18:29 2010
Stack: openais
Current DC: srv01 - partition with quorum
Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b
2 Nodes configured, 2 expected votes
1 Resources configured.
============
Online: [ srv01 srv02 ]
Resource Group: UMgroup01
UmVIPcheck (ocf::heartbeat:Dummy): Started srv01
UmIPaddr (ocf::heartbeat:Dummy2): Started srv01
The error of the UmIPaddr resource of this time set it in block.。
<group id="UMgroup01">
<primitive class="ocf" type="Dummy" provider="heartbeat" id="UmVIPcheck">
<operations>
<op id="op-umVIPcheck-start" interval="0" name="start" timeout="90s" on-fail="restart"
start-delay="2s"/>
</operations>
</primitive>
<primitive class="ocf" type="Dummy2" provider="heartbeat" id="UmIPaddr">
<operations>
<op id="op-umIPaddr-start" interval="0" name="start" timeout="60s" on-fail="restart"/>
<op id="op-umIPaddr-monitor" interval="10" name="monitor" timeout="60s"
on-fail="restart"/>
<op id="op-umIPaddr-stop" interval="0" name="stop" timeout="60s" on-fail="block"/>
</operations>
</primitive>
</group>
UmVIPcheck moves to a srv02 node when I generate a stop error in UmIPaddr artificially then.
UmIPaddr does not move.
============
Last updated: Mon Aug 9 11:19:19 2010
Stack: openais
Current DC: srv01 - partition with quorum
Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b
2 Nodes configured, 2 expected votes
1 Resources configured.
============
Online: [ srv01 srv02 ]
Resource Group: UMgroup01
UmVIPcheck (ocf::heartbeat:Dummy): Started srv02
UmIPaddr (ocf::heartbeat:Dummy2): Started srv01 (unmanaged) FAILED
Failed actions:
UmIPaddr_stop_0 (node=srv01, call=8, rc=1, status=complete): unknown error
Setting of UmIPaddr acted and thought that UmVIPcheck did not move.(on-fail="block")
I have forgotten whether this movement was specifications.
Is this movement specifications?
Was there the setting that did not move other group resources?(not move UmVIPcheck)
Best Regards,
Hideo Yamauchi.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cib.xml.1232.mini
Type: application/octet-stream
Size: 2182 bytes
Desc: 2729678951-cib.xml.1232.mini
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100809/fa982dea/attachment-0003.obj>
More information about the Pacemaker
mailing list