On 3 November 2013 14:24, Takatoshi MATSUO wrote:
> Hi Richard
>
> 2013/11/3 Richard Colley :
> >>
> >> This ?
> >>
> >>
> https://github.com/t-matsuo/resource-agents/wiki/Resource-agent-for-postgresql-9.2-for-disaster(split)-site
> >>
> >> You can use rep_mode="slave".
> >>
> >> Takatoshi MATSUO
Hi, Andrew
I tested by this commitment.
https://github.com/beekhof/pacemaker/commit/145c782e432d8108ca865f994640cf5a62406363
However, the problem has not improved.
It seems that it will be preferentially processed since the message of
CPG is set as G_PRIORITY_MED.
I suggest that you lower the pr
Hi Andrew, David, all,
Just found interesting fact, don't know is it a bug or not.
When doing service pacemaker stop on a node which has drbd resource
promoted, that resource does not promote on another node, and promote
operation timeouts.
This is related to drbd fence integration with pacemake
Thanks I had just found that... I reset my thresholds
All seems to be working again !!
alex
From: emmanuel segura [mailto:emi2f...@gmail.com]
Sent: Monday, 4 November 2013 7:25 PM
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] problem with config
http://clusterlabs.org/doc/
http://clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-failure-migration.html
2013/11/4 Alex Samad - Yieldbroker
> Hi
>
>
> I have attached my config at the bottom. But very basically when 1
> resource is failing it is not restarting on the other node ? strangely this
> used