what the blog?

{upgrade in progress..}

Pacemaker non-clones resource restart when clones stop/start on other nodes

Scenario

Node alpha holds resource groups rg_vg01.

Node beta holds the corresponding resources as same as alpha

Both nodes hold instances of the CLVM DLM clone.

As beta is switched into standby mode, the clone
instance on beta correctly transition to the Stopped state.
However, the rg_vg01 resource groups are
restarted in-place on alpha needlessly.

Solution

It was caused by resource-stickness score INFINITY order was defined between clone and standalone resource.
eg:

order order-clvm-vg inf: clvm-dlm-clone rg_vg01

To solve that, you should change the score to 0 between standalone and clones.
like:

order order-clvm-vg 0: clvm-dlm-clone rg_vg01

A related bug fix.
http://hg.clusterlabs.org/pacemaker/stable-1.0/rev/f17e29306fa1

linux

levin • July 3, 2010


Previous Post

Next Post

Leave a Reply