Re: [ClusterLabs] Master-Slaver resource Restarted after configuration change

On 06/29/2016 01:35 PM, Ilia Sokolinski wrote: > >> >> I'm not sure there's a way to do this. >> >> If a (non-reloadable) parameter changes, the entire clone does need a >> restart, so the cluster will want all instances to be stopped, before >> proceeding to start them all again. >> >> Your

Re: [ClusterLabs] Master-Slaver resource Restarted after configuration change

Ilia Sokolinski 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

[ClusterLabs] Master-Slaver resource Restarted after configuration change

Hi, 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