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
>> 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
>
its for a failover
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
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 very long time. I checked it and
it seems that pacemaker wai
