Hi all.
For what reason is implemented PGSQL.lock in RA, and what pbs may happen
if it'll be removed from RA code?
Also, 2nd question: how I can prevent pgsql RA from promoting master
before both nodes will brings up OR before timeout is reached (for ex.,
if 2nd node is dead)? I think that cl
On Fri, Feb 08, 2013 at 11:21:15AM +0100, Lars Ellenberg wrote:
> On Mon, Aug 13, 2012 at 02:07:46PM +0200, Dejan Muhamedagic wrote:
Appologies, I did not look at the date of the Post.
For some reason it appeart as "first unread", and I assumed it was
recent. D'oh.
:-)
> Please use resource-age
On Mon, Aug 13, 2012 at 02:07:46PM +0200, Dejan Muhamedagic wrote:
> Hi,
>
> On Mon, Jul 30, 2012 at 12:09:10PM -0400, Jake Smith wrote:
> >
> > - Original Message -
> > > From: "Julien Cornuwel"
> > > To: pacemaker@oss.clusterlabs.org
> > > Sent: Wednesday, July 25, 2012 5:51:28 AM
> >
Ah, thanks for clearing that up. I must have been doing something wrong before
as I've managed to get it to work now.
Regards,
James
On Feb 7, 2013, at 4:42 PM, David Vossel wrote:
>
>
> - Original Message -
>> From: "James Guthrie"
>> To: "The Pacemaker cluster resource manager"
>
Hi,
Please add the pcmk_off_timeout and pcmk_reboot_timeout parameters
to the output of 'stonithd metadata',
because ERROR message is output when I load configuration file which
set the pcmk_off_timeout/pcmk_reboot_timeout parameter by crmsh.
- pacemaker-1.1.8 : b5a04ac015 (the latest devel)
- cr
