[ClusterLabs] Master-Slaver resource Restarted after configuration change

Ferenc Wágner wferi at niif.hu
Fri Jun 10 03:13:48 EDT 2016

Ilia Sokolinski <ilia at clearskydata.com> writes:

> We have a custom Master-Slave resource running on a 3-node pcs cluster on CentOS 7.1
> As part of what is supposed to be an NDU we do update some properties of the resource.
> For some reason this causes both Master and Slave instances of the  resource to be restarted.
> Since restart takes a fairly long time for us, the update becomes very much disruptive.
> Is this expected? 

Yes, if you changed a parameter declared with unique="1" in your resource
agent metadata.

> We have not seen this behavior with the previous release of pacemaker.

I'm surprised...

More information about the Users mailing list