This article describes fencing considerations, quorum settings, and commands for sensible behavior in a 2-node Pacemaker with Corosync cluster Goals for a 2-node cluster: Do not go online with stale data (replication case). Do not cause a startup fencing loop. Run Pacemaker primitive services exactly once (prevent IP conflicts, data corruption, and other issues). To be allowed to start services, a node needs to be quorate, that is, the node needs to be a member of a cluster partition that has...
