[Pacemaker] Master going into Stopped after stop operation times out

Andrew Beekhof andrew at beekhof.net
Wed Jan 16 23:01:05 UTC 2013


On Sun, Jan 13, 2013 at 4:39 AM, Parshvi <parshvi.17 at gmail.com> wrote:
>
>> Location rule needs to specify the role otherwise the slave never runs since
> it can't run on same node i.e.:
>> location Redis_Master_Prefers_Node MS_Redis_Server $role="Master" 1: ct-node-
> ft-112
>>
>> May want an order statement too so that the IP comes before/after the MS
> resource promotes.
>
> Neither master nor slave is started once stop times out,

I've already explained this to you in the bugzilla comments.
The cluster cannot make progress if stop actions fail and stonith is disabled.
You need to resolve the error manually.

> even
> after the applying the changes in config.
> Changed config is as follows:
>
> primitive Redis ocf:PhoenixFT:RedisRA \
>   meta failure-timeout="1ms" target-role="Started" \
>   op stop interval="0" timeout="5s" on-fail="restart" \
>   op monitor interval="6s" role="Master" timeout="300s" \
>   op monitor interval="5s" role="Slave" timeout="300s"
> primitive RedisClusterIP ocf:heartbeat:IPaddr2 \
>   params ip="192.168.129.242" nic="eth3" cidr_netmask="24" \
>   op monitor interval="5s" timeout="60s" \
>   meta resource-stickiness="1" is-managed="true"
> ms MS_Redis_Server Redis \
>   meta master-max="1" master-node-max="1" clone-node-max="1" clone-max="2"
> target-role="Master" notify="true" globally-unique="false" failure-timeout="1ms"
> is-managed="true"
>
> location Redis_Prefers_Node MS_Redis_Server \
>   rule $id="Redis_Prefers_Node-rule" $role="Master" 1: #uname eq ct-node-ft-112
>
> colocation IP_With_Master_Redis inf: RedisClusterIP MS_Redis_Server:Master
>
> order Redis-ordered-group inf: ( MS_Redis_Server:promote ) (
> RedisClusterIP:start )
>
> Snapshot of crm_mon:
> RedisClusterIP  (ocf::heartbeat:IPaddr2):       Started ct-node-ft-112
>  Master/Slave Set: MS_Redis_Server [Redis]
>      Masters: [ ct-node-ft-112 ]
>      Stopped: [ Redis:1 ]
>
> Additional info:
> crm(live)resource# failcount MS_Redis_Server show ct-node-ft-112
> scope=status  name=fail-count-MS_Redis_Server value=0
> crm(live)resource# failcount MS_Redis_Server show ct-node-ft-93
> scope=status  name=fail-count-MS_Redis_Server value=0
> crm(live)resource# failcount Redis show ct-node-ft-93
> scope=status  name=fail-count-Redis value=INFINITY
> crm(live)resource# failcount Redis show ct-node-ft-112
> scope=status  name=fail-count-Redis value=0
>
> Is there something else we are missing ?
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org




More information about the Pacemaker mailing list