Re: [ClusterLabs] How can I prevent multiple start of IPaddr 2 in an environment using fence_mpath?

Hi, Andrei Thanks for your comment. We are not assuming node level fencing in the current environment. I tried the power_timeout setting that you taught. However, fence_mpath immediately returns the status off when you execute the off action.

Re: [ClusterLabs] No slave is promoted to be master

On Tue, 17 Apr 2018 04:16:38 + 范国腾 wrote: > I check the status again. It is not not promoted but it promoted about 15 > minutes after the cluster starts. > > I try in three labs and the results are same: The promotion happens 15 > minutes after the cluster starts. >

Re: [ClusterLabs] Booth fail-over conditions

Hi, On Mon, Apr 16, 2018 at 01:22:08PM +0200, Kristoffer Grönlund wrote: > Zach Anderson writes: > > > Hey all, > > > > new user to pacemaker/booth and I'm fumbling my way through my first proof > > of concept. I have a 2 site configuration setup with local pacemaker >

Re: [ClusterLabs] How can I prevent multiple start of IPaddr 2 in an environment using fence_mpath?

Hi, Ken Thanks for your comment. Network fencing that's a valid means, I also think. However, I think that the reliance on equipment is strong. Since we do not have an SNMP-capable network switch in our environment, we can not immediately try it. Thanks, Yusuke > -Original Message- >

[ClusterLabs] 答复: No slave is promoted to be master

Thank you very much, Rorthais, I see now. I have two more questions. 1. If I change the "cluster-recheck-interval" parameter from the default 15 minutes to 10 seconds, is there any bad impact? Could this be a workaround? 2. This issue happens only in the following configuration.