On Sun, Jan 13, 2013 at 4:39 AM, Parshvi 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 tha
> 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
> 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.
- Original Message -
> From: "Parshvi"
> To: pacema...@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
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
