Hi,
I created a cluster installation with two nodes. Everything is running
smoothly most of the time. But in case a resource was switched into
unmanaged state and I reboot the node on which the resource is running,
corosync is hanging during stop. Only after 'shutdown-escalation' time
corosync is stopping.
Is this normal behavior ? Is there a parameter to prevent this ? IMHO a
unmanged resource should not prevent corosync from stopping.
What's the expected behaviour on the other node ?
My environment :
Scientific Linux 6.3
pacemaker-cluster-libs-1.1.7-6.el6.x86_64
pacemaker-cli-1.1.7-6.el6.x86_64
pacemaker-libs-1.1.7-6.el6.x86_64
pacemaker-1.1.7-6.el6.x86_64
corosynclib-1.4.1-7.el6.x86_64
corosync-1.4.1-7.el6.x86_64
resource-agents-3.9.2-12.el6.x86_64
cluster-glue-libs-1.0.5-6.el6.x86_64
cluster-glue-1.0.5-6.el6.x86_64
Thanks for any hints !
Kind regards,
Detlef
_______________________________________________
Pacemaker mailing list: Pacemaker@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
