[Pacemaker] pacemaker shutdown waits for a failover

Andrew Beekhof andrew at beekhof.net
Sun Jul 27 19:08:43 EDT 2014


On 28 Jul 2014, at 12:40 am, Liron Amitzi <LironA at imperva.com> 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 very long time. I checked it and it seems that pacemaker waits until the failover is complete before stopping. I expect it to stop the resources, initiate the failover and stop, not wait until everything is up on the other node.

Thats what I would expect too.
Can you show us something that would suggest this isn't happening?

> Am i missing something? Is this expected?
> Thanks,
> Liron
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140728/097710d8/attachment-0003.sig>


More information about the Pacemaker mailing list