[ClusterLabs] Master-Slaver resource Restarted after configuration change

2016-06-09 Thread Ilia Sokolinski
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 f

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

2016-06-10 Thread Ferenc Wágner
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 the resource > to be r

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

2016-06-10 Thread Ilia Sokolinski
Feri, Thanks for the answer - this is very useful. Ilia > On Jun 10, 2016, at 3:13 AM, Ferenc Wágner wrote: > > 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

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

2016-06-28 Thread Ilia Sokolinski
Feri, I have a follow-up question: We are trying to achieve an NDU for our Master/Slave resource - this is why the resource parameter is being updated. The desired sequence of events is as follows: Resource parameter is updated in pacemaker. Slave instance is reloaded (or restarted) to pickup t

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

2016-06-28 Thread Ken Gaillot
On 06/28/2016 04:10 PM, Ilia Sokolinski wrote: > Feri, > > > > I have a follow-up question: > > We are trying to achieve an NDU for our Master/Slave resource - this is > why the resource parameter is being updated. > The desired sequence of events is as follows: > > 1. Resource parameter is

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

2016-06-29 Thread Ilia Sokolinski
> > 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 desired behavior couldn't be the default, because not all s

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

2016-06-29 Thread Ken Gaillot
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 desir