[ClusterLabs] Different pacemaker versions split cluster

Hi, I had 4 nodes with Ubuntu 14.04LTS in my cluster and all of then worked well. I need upgrade all my cluster nodes to Ubuntu 16.04LTS without stop my resources. Two nodes have been updated to 16.04 and the two others remains with 14.04. The problem is that my cluster was splited and the

Re: [ClusterLabs] Three node cluster constraint

I've do more searching, and found "crm_simulate -sL" tool, it says: native_color: vip-slave allocation score on node1: 100 native_color: vip-slave allocation score on node2: 50 native_color: vip-slave allocation score on node3: INFINITY seems 'pcs constraint colocation add vip-slave with Slave

[ClusterLabs] Fwd: Three node cluster constraint

sorry, I've sent to the wrong mailist, fwd to users@clusterlabs.org -- Forwarded message -- From: wd Date: Tue, May 31, 2016 at 12:04 PM Subject: Three node cluster constraint To: pacema...@oss.clusterlabs.org Hi, I've setup a three node PostgreSQL cluster,

Re: [ClusterLabs] How to use totem.interface.dynamic for corosync ?

I'll try corosync 2.x So I need to edit configuration files on all node then call corosync-cfgtool -R or on one node is ok? On Fri, May 27, 2016 at 6:28 PM, Jan Friesse wrote: > hi, >> >> I use corosync with udpu ( since multi broadcast not work here), and want >> the

Re: [ClusterLabs] fence_sanlock and pacemaker

[adding sanlock-devel ML into the loop as deemed appropriate] On 18/05/16 12:49 +, Da Shi Cao wrote: > After some try and error, fence_sanlock can be used as a stonith > resource in pacemaker+corosync. > 1. Add a "monitor" action, which is exactly the same action as > "status". Per

[ClusterLabs] Creating a rule based on whether a quorum exists

Hi All, I have a two-node cluster with no-quorum-policy=ignore and an external ping responder to try to determine if a node has its network down (it's the dead one), or if the other node is really dead.. The ping helps to determine who the master is. I have realised in the situation where the