Re: [Pacemaker] Time-based resource stickiness not working cleanly

2012-07-05 Thread Jake Smith
- Original Message - > From: "Prakash Velayutham" > To: "Jake Smith" , "The Pacemaker cluster resource > manager" > Sent: Wednesday, June 27, 2012 5:39:51 PM > Subject: Re: [Pacemaker] Time-based resource stickiness not working cleanly &

Re: [Pacemaker] Time-based resource stickiness not working cleanly

2012-06-27 Thread Velayutham, Prakash
Hi Jake, On Jun 27, 2012, at 4:42 PM, Jake Smith wrote: > - Original Message - >> From: "Prakash Velayutham" >> To: "The Pacemaker cluster resource manager" >> Sent: Wednesday, June 27, 2012 4:06:39 PM >> Subject: Re: [Pacemaker] Tim

Re: [Pacemaker] Time-based resource stickiness not working cleanly

2012-06-27 Thread Jake Smith
- Original Message - > From: "Prakash Velayutham" > To: "The Pacemaker cluster resource manager" > Sent: Wednesday, June 27, 2012 4:06:39 PM > Subject: Re: [Pacemaker] Time-based resource stickiness not working cleanly > > I created a simple IPa

Re: [Pacemaker] Time-based resource stickiness not working cleanly

2012-06-27 Thread Velayutham, Prakash
I created a simple IPaddr2 resource for this testing. 1. I can confirm that this resource (with just a location preference constraint and nothing else) does not get restarted when a node reboots. So must be something with the clone/group resources. Not sure how to debug right now. 2. I have a ti

Re: [Pacemaker] Time-based resource stickiness not working cleanly

2012-06-27 Thread Velayutham, Prakash
I am all for testing, but looks like our database person wants this completed now. I will test this in our dev. environment soon. Thanks, Prakash On Jun 27, 2012, at 2:44 PM, Phil Frost wrote: > On 06/27/2012 02:33 PM, Velayutham, Prakash wrote: >> and the cluster works fine, except that when t

Re: [Pacemaker] Time-based resource stickiness not working cleanly

2012-06-27 Thread Phil Frost
On 06/27/2012 02:33 PM, Velayutham, Prakash wrote: 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

Re: [Pacemaker] Time-based resource stickiness not working cleanly

2012-06-27 Thread 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 scenario

Re: [Pacemaker] Time-based resource stickiness not working cleanly

2012-06-27 Thread Phil Frost
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 i

Re: [Pacemaker] Time-based resource stickiness not working cleanly

2012-06-26 Thread Velayutham, Prakash
Hi, Initially I had the following resource setup. 1. Clone -> Group -> Primitives (ocf:pacemaker:controld, ocf:ocfs2:o2cb) 2. Clone -> Primitives (ocf:heartbeat:Filesystem) 3. Group -> Primitives (ocf:heartbeat:IPaddr2, ocf:heartbeat:mysql) I had a resource colocation where 3, 2 and 1 would all

Re: [Pacemaker] Time-based resource stickiness not working cleanly

2012-06-26 Thread Phil Frost
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). Ever

[Pacemaker] Time-based resource stickiness not working cleanly

2012-06-26 Thread Velayutham, Prakash
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 ge