[Pacemaker] Time-based resource stickiness not working cleanly

[Velayutham, Prakash]

Yeah, after reading that doc is why I went with the original config that I had.

I am having to run 2 MySQL instances each on its own OCFS2 volume. The volumes are mounted on both the nodes, but I have location preference so 1 instance runs on each node if possible. I am able to test all scenarios (private network down, public network down, pulling fiber channel out, kernel panic) and the cluster works fine, except that when the fenced (STONITHed) node comes back up and joins the cluster, all resources (including the one that is running in its preferred location) gets restarted.

This is annoying and I am trying to find out why this is. I started another thread for that exact issue this morning and I have shared the relevant portions of my CIB there. Please let me know if you see anything there that could cause this.

Thanks,
Prakash

On Jun 27, 2012, at 2:20 PM, Phil Frost wrote:

> On 06/26/2012 04:33 PM, Velayutham, Prakash wrote:
>> Any idea? Can a resource order constraint be specified depending on a primitive that is part of a clone resource? Is that even supported?
> 
> Probably not. Usually you'd want to have your constraints reference the clone, not the primitive behind it. More here:
> 
> http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/ch10s02s05.html