[ClusterLabs] cluster with two ESX server

hi@all, in my configuration, the 1st Node run on ESX1, the second run on ESX2. Now I'm looking for a way to configure the cluster fence/stonith with two ESX server - is this possible? I try to us fence_vmware with vcenter, but then the vcenter is a single point of failure und running two

Re: [ClusterLabs] Pacemaker responsible of DRBD and a systemd resource

On Mon, 2017-11-13 at 10:24 -0500, Derek Wuelfrath wrote: > Hello Ken ! > > > Make sure that the systemd service is not enabled. If pacemaker is > > managing a service, systemd can't also be trying to start and stop > > it. > > It is not. I made sure of this in the first place :) > > > Beyond

Re: [ClusterLabs] Low priority colocation

On Fri, 2017-11-24 at 11:32 +, Alan Birtles wrote: > Is it possible to setup pacemaker with a resource which will only run > on the same machine as another resource but that will not trigger a > failover of the second resource if the first resource becomes > unrunnable? > e.g. > I have 2

Re: [ClusterLabs] pcs create master/slave resource doesn't work

On Fri, 2017-11-24 at 18:00 +0800, Hui Xiang wrote: > Jan, > >   Very appreciated on your help, I am getting further more, but still > it looks very strange. > > 1. To use "debug-promote", I upgrade pacemaker from 1.12 to 1.16, pcs > to 0.9.160. > > 2. Recreate resource with below commands >

Re: [ClusterLabs] Is corosync supposed to be restarted if it fies?

Отправлено с iPhone > 27 нояб. 2017 г., в 14:36, Ferenc Wágner написал(а): > > Andrei Borzenkov writes: > >> 25.11.2017 10:05, Andrei Borzenkov пишет: >> >>> In one of guides suggested procedure to simulate split brain was to kill >>> corosync process.

[ClusterLabs] Pacemaker resource is not tried to be recovered after failure on slave node even when failcount is less than migration-threshold

Hi, Could you please help me with below query. I have a stateful resource, stateful_ms, defined as below. The migration-threshold is defined as 4 and resource-stickiness as 100. I have pacemaker cluster of 5 nodes. First time resource(stateful_ms) is up as MASTER on node-0 and as slave in other

Re: [ClusterLabs] Is corosync supposed to be restarted if it fies?

Andrei Borzenkov writes: > 25.11.2017 10:05, Andrei Borzenkov пишет: > >> In one of guides suggested procedure to simulate split brain was to kill >> corosync process. It actually worked on one cluster, but on another >> corosync process was restarted after being killed

[ClusterLabs] Antw: SBD stonith in 2 node cluster - how to make it prefer one side of cluster?

Hi! With an sbd running on each node, I think it doesn't make a big differentce wich one was started first in cas eof a split brain: There is a chance that both nodes will kill each other. I'd put my efforts into redundant reliable networking instead (MHO)... Regards, Ulrich > Wrapping my