[Pacemaker] Problem understanding resource stickyness

[David Vossel]

----- Original Message -----
> From: "Bernhard Schmidt" <berni at birkenwald.de>
> To: pacemaker at clusterlabs.org
> Sent: Wednesday, April 25, 2012 2:25:42 PM
> Subject: Re: [Pacemaker] Problem understanding resource stickyness
> 
> David Vossel <dvossel at redhat.com> wrote:
> 
> Hello David,
> 
> 
> >> colocation vm-greatfw1 inf: kvm-greatfw1 ms-drbd-greatfw1:Master
> >> colocation vm-greatfw2 inf: kvm-greatfw2 ms-drbd-greatfw2:Master
> >> colocation col-greatfw1-greatfw2 -2000: kvm-greatfw1 kvm-greatfw2
> >
> > Switch the order on the above colocation constraint to look like
> > this.
> >
> > colocation col-greatfw1-greatfw2 -2000: kvm-greatfw2 kvm-greatfw1
> >
> > Where kvm-greatfw1 is is the with-rsc argument... Basically just
> > reverse the two resources.  This fixed it for me, but I'm not
> > convinced this isn't a bug.  I'm looking further into this.
> 
> Thanks, this fixed the problem indeed.

Awesome :)

Here's another observation I've made.

Using your original configuration, if you set the resource-stickiness higher on kvm-greatfw1 than the -2000 colocation score, kvm-greatfw1 will stay put... but kvm-greatfw2 will not move either, which also seems undesirable.

-- Vossel


> Best Regards,
> Bernhard
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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
>