Re: [ClusterLabs] why is node fenced ?

- Am 14. Aug 2019 um 19:07 schrieb kgaillot kgail...@redhat.com: >> That's my setting: >> >> expected_votes: 2 >> two_node: 1 >> wait_for_all: 0 >> >> no-quorum-policy=ignore >> >> I did that because i want be able to start the cluster although one >> node has e.g. a hardware

Re: [ClusterLabs] 2-node DRBD Pacemaker not performing as expected: Where to next?

On Thu, 2019-08-15 at 11:25 -0400, Nickle, Richard wrote: > > My objective is two-node active/passive DRBD device which would > automatically fail over, a secondary objective would be to use > standard, stock and supported software distributions and repositories > with as little customization as

Re: [ClusterLabs] [Announce] clufter v0.77.2 released

On 14/08/19 16:26 +0200, Jan Pokorný wrote: > I am happy to announce that clufter, a tool/library for transforming > and analyzing cluster configuration formats, got its version 0.77.2 > tagged and released (incl. signature using my 60BCBB4F5CD7F9EF key): >

[ClusterLabs] Master Postgresql in Cluster has high CPU load with idling processes

Hi, Postgres Version: 9.6 OS: RHEL 6.9 We have a Postgres Cluster of 4 nodes in active-passive mode. Cluster set up is A, B, C, D virtual machines. A is master, synchronizes to B and C. C synchronizes to D. B, C and D are slaves. A and B are on Prod server. C and D are on DR server. A is

[ClusterLabs] 2-node DRBD Pacemaker not performing as expected: Where to next?

My objective is two-node active/passive DRBD device which would automatically fail over, a secondary objective would be to use standard, stock and supported software distributions and repositories with as little customization as possible. I'm using Ubuntu 18.04.3, plus the DRBD, corosync and

Re: [ClusterLabs] cloned ethmonitor - upon failure of all nodes

Thanks for the tips on the constraint rules. I currently have two separate constraint for each ethmonitor - I did not realise that you could have a constraint rule that can combine multiple ethmonitors. Based on your suggestion, I have now used one constraint, as such: score=-INFINITY

Re: [ClusterLabs] cloned ethmonitor - upon failure of all nodes

I have tried both ifdown and using vmware to disconnect the interface from the VM. It is likely a constraint issue, as I don't have much experience with corosync/pacemaker. On Thu, 15 Aug 2019 at 14:01, Jan Pokorný wrote: > On 15/08/19 10:59 +0100, solarmon wrote: > > I have a two node cluster

Re: [ClusterLabs] cloned ethmonitor - upon failure of all nodes

On Thu, 2019-08-15 at 10:59 +0100, solarmon wrote: > Hi, > > I have a two node cluster setup where each node is multi-homed over > two separate external interfaces - net4 and net5 - that can have > traffic load balanced between them. > > I have created multiple virtual ip resources (grouped

Re: [ClusterLabs] cloned ethmonitor - upon failure of all nodes

On 15/08/19 10:59 +0100, solarmon wrote: > I have a two node cluster setup where each node is multi-homed over two > separate external interfaces - net4 and net5 - that can have traffic load > balanced between them. > > I have created multiple virtual ip resources (grouped together) that should >

[ClusterLabs] cloned ethmonitor - upon failure of all nodes

Hi, I have a two node cluster setup where each node is multi-homed over two separate external interfaces - net4 and net5 - that can have traffic load balanced between them. I have created multiple virtual ip resources (grouped together) that should only be active on only one of the two nodes. I