[ClusterLabs] 答复: Pacemaker Master restarts when Slave is added to the cluster

2017-12-27 Thread 范国腾
Andrei, I set the interleave=true and it does not restart any more. Thank you very much. A word of you resolves the problem confusing my several days  -邮件原件- 发件人: Andrei Borzenkov [mailto:arvidj...@gmail.com] 发送时间: 2017年12月27日 19:06 收件人: Cluster Labs - All topics related to

Re: [ClusterLabs] crmsh resource failcount does not appear to work

2017-12-27 Thread Kristoffer Grönlund
Andrei Borzenkov writes: > As far as I can tell, pacemaker acts on failcount attributes qualified > by operation name, while crm sets/queries unqualified attribute; I do > not see any syntax to set fail-count for specific operation in crmsh. crmsh uses crm_attribute to get

Re: [ClusterLabs] Pacemaker Master restarts when Slave is added to the cluster

2017-12-27 Thread Andrei Borzenkov
Usual suspect - interleave=false on clone resource. On Wed, Dec 27, 2017 at 10:49 AM, 范国腾 wrote: > Hello, > > > > In my test environment, I meet one issue about the pacemaker: when a new > node is added in the cluster, the master node restart. This issue will lead > to the

Re: [ClusterLabs] crmsh resource failcount does not appear to work

2017-12-27 Thread Andrei Borzenkov
On Wed, Dec 27, 2017 at 11:40 AM, Kristoffer Grönlund wrote: > > Andrei Borzenkov writes: > > > As far as I can tell, pacemaker acts on failcount attributes qualified > > by operation name, while crm sets/queries unqualified attribute; I do > > not see