[ClusterLabs] ClusterIP won't return to recovered node

Klaus Wenninger kwenning at redhat.com
Mon Jun 12 10:23:19 EDT 2017

On 06/12/2017 04:02 PM, Ken Gaillot wrote:
> On 06/10/2017 10:53 AM, Dan Ragle wrote:
>> So I guess my bottom line question is: How does one tell Pacemaker that
>> the individual legs of globally unique clones should *always* be spread
>> across the available nodes whenever possible, regardless of the number
>> of processes on any one of the nodes? For kicks I did try:
>> pcs constraint location ClusterIP:0 prefers node1-pcs=INFINITY
>> but it responded with an error about an invalid character (:).
> There isn't a way currently. It will try to do that when initially
> placing them, but once they've moved together, there's no simple way to
> tell them to move. I suppose a workaround might be to create a dummy
> resource that you constrain to that node so it looks like the other node
> is less busy.

Another ugly dummy resource idea - maybe less fragile -
and not tried out:
One could have 2 dummy resources that would rather like
to live on different nodes - no issue with primitives - and
do depend collocated on ClusterIP.
Wouldn't that pull them apart once possible?

> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

Klaus Wenninger

Senior Software Engineer, EMEA ENG Openstack Infrastructure

Red Hat

kwenning at redhat.com   

More information about the Users mailing list