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

Parshvi parshvi.17 at gmail.com
Sat Jan 12 12:39:34 EST 2013

> 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-
> 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, 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="" 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" 

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 ?

More information about the Pacemaker mailing list