Re: [Pacemaker] no-quorum-policy = demote?

2014-04-10 Thread Alexandre
Le 10 avr. 2014 15:44, "Christian Ciach" a écrit : > > I don't really like the idea to periodically poll "crm_node -q" for the current quorum state. No matter how frequently the monitor-function gets called, there will always be a small time frame where both nodes will be in the master state at th

Re: [Pacemaker] Node stuck in pending state

2014-04-10 Thread Andrew Beekhof
On 11 Apr 2014, at 12:29 am, Brian J. Murrell wrote: > On Thu, 2014-04-10 at 10:04 +1000, Andrew Beekhof wrote: >> >> Brian: the detective work above is highly appreciated > > NP. I feel like I am getting better at reading these logs and can > provide some more detailed dissection of them.

Re: [Pacemaker] Node stuck in pending state

2014-04-10 Thread Brian J. Murrell
On Thu, 2014-04-10 at 10:04 +1000, Andrew Beekhof wrote: > > Brian: the detective work above is highly appreciated NP. I feel like I am getting better at reading these logs and can provide some more detailed dissection of them. And am happy to do so to help get to the bottom of things. :-) >

Re: [Pacemaker] no-quorum-policy = demote?

2014-04-10 Thread Christian Ciach
I don't really like the idea to periodically poll "crm_node -q" for the current quorum state. No matter how frequently the monitor-function gets called, there will always be a small time frame where both nodes will be in the master state at the same time. Is there a way to get a notification to th