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

Jake Smith jsmith at argotec.com
Fri Jan 11 18:40:15 UTC 2013


----- Original Message -----
> From: "Parshvi" <parshvi.17 at gmail.com>
> To: pacemaker at clusterlabs.org
> Sent: Friday, January 11, 2013 1:16:27 PM
> Subject: [Pacemaker] Master going into Stopped after stop operation times out
> 
> We are expecting Master to be demoted to Slave but it goes into
> Stopped state.
> The Slave is though properly promoted and running as Master:
> 
> Master/Slave Set: MS_Redis_Server [Redis]
>      Masters: [ ct-node-ft-112 ]
>      Stopped: [ Redis:1 ]
> 
> The config details are :
> 
> 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"
> 
> 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"
> 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"
> 
> location Redis_Prefers_Node MS_Redis_Server 1: ct-node-ft-112

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.

HTH

Jake

> colocation IP_With_Master_Redis inf: RedisClusterIP
> MS_Redis_Server:Master
> 
> property $id="cib-bootstrap-options" \
>         dc-version="1.1.8-2.el5-394e906" \
>         cluster-infrastructure="openais" \
>         expected-quorum-votes="2" \
>         stonith-enabled="false" \
>         no-quorum-policy="ignore" \
>         start-failure-is-fatal="false" \
>         batch-limit="40" \
>         last-lrm-refresh="1357911794"
> 
> The service remains stopped forever. Is there something wrong in the
> way, we
> have configured the Master Slave?
> 
> 
> 
> _______________________________________________
> 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