On 3 Aug 2014, at 4:07 pm, Liron Amitzi wrote:
> When I run "service pacemaker stop" it takes a long time, I see that it
> stops all the resources, then starts them on the other node, and only
> then the "stop" command is completed.
Ahhh! It was the DC.
It app
When I run "service pacemaker stop" it takes a long time, I see that it
stops all the resources, then starts them on the other node, and only then
the "stop" command is completed.
>>>
>>> Ahhh! It was the DC.
>>>
>>> It appears to be deliberate, I found this commit from 2008 where
On 31 Jul 2014, at 8:20 pm, Liron Amitzi wrote:
>>> When I run "service pacemaker stop" it takes a long time, I see that it
>>> stops all the resources, then starts them on the other node, and only then
>>> the "stop" command is completed.
>>
>> Ahhh! It was the DC.
>>
>> It appears to be de
>> When I run "service pacemaker stop" it takes a long time, I see that it
>> stops all the resources, then starts them on the other node, and only then
>> the "stop" command is completed.
>
>Ahhh! It was the DC.
>
>It appears to be deliberate, I found this commit from 2008 where the behaviour
>
15:27:09 [28023] ha1 pacemakerd: info: main:Exiting pacemakerd
>
>
>
>
> From: Andrew Beekhof
> Sent: Monday, July 28, 2014 2:08
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] pacemaker shutdown waits for a
shutdown_worker:
Shutdown complete
Jun 29 15:27:09 [28023] ha1 pacemakerd: info: main:Exiting pacemakerd
From: Andrew Beekhof
Sent: Monday, July 28, 2014 2:08
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] pacemaker shutdown wa
On 28 Jul 2014, at 12:40 am, Liron Amitzi wrote:
> Hi guys,
> I'm working with pacemaker 1.1.7-6 with corosync 1.4.1-15 (2 nodes) and
> facing a strange behavior.
> I have several resources including Oracle database, and when I try to stop
> the pacemaker or reboot the active node it takes a v
