On 06/26/2012 12:59 PM, Velayutham, Prakash wrote:
Hi,
I have a Corosync (1.3.0-5.6.1) / Pacemaker (1.1.5-5.5.5) cluster
where I am using a Time-based rule for resource stickiness
(http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-rules-cluster-options.html).
Everything works as expected, except that the resources get stopped
and restarted on the same node during the core-hours if any other node
in the cluster gets rebooted. The stickiness works, but I would prefer
that the resources do not get affected this way. Would anyone know
what I have configured wrong?
If you delete your time-based rules, do you still have these undesired
restarts? Maybe the restarts are due to something else entirely, like
maybe an order constraint on a clone. There was a bug some time ago
regarding this, but I've found configurations where it's still a
problem. More here:
https://developerbugs.linuxfoundation.org/show_bug.cgi?id=2153
_______________________________________________
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
