<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/26/2012 12:59 PM, Velayutham,
Prakash wrote:<br>
</div>
<blockquote
cite="mid:CFD613AA-9636-4A56-81FE-7EB9E9DE6E9A@cchmc.org"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
Hi,<br>
<br>
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 (<a
moz-do-not-send="true"
href="http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-rules-cluster-options.html">http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-rules-cluster-options.html</a>).<br>
<br>
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?<br>
</blockquote>
<br>
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:<br>
<br>
<a class="moz-txt-link-freetext" href="https://developerbugs.linuxfoundation.org/show_bug.cgi?id=2153">https://developerbugs.linuxfoundation.org/show_bug.cgi?id=2153</a><br>
</body>
</html>