[Pacemaker] Y should pacemaker be started simultaneously.

[Andrei Borzenkov]

On Mon, Oct 6, 2014 at 9:03 AM, Digimer <lists at alteeve.ca> wrote:
> If stonith was configured, after the time out, the first node would fence
> the second node ("unable to reach" != "off").
>
> Alternatively, you can set corosync to 'wait_for_all' and have the first
> node do nothing until it sees the peer.
>

Am I right that wait_for_all is available only in corosync 2.x and not in 1.x?

> To do otherwise would be to risk a split-brain. Each node needs to know the
> state of the peer in order to run services safely. By having both start at
> the same time, then they know what the other is doing. By disabling quorum,
> you allow one node to continue to operate when the other leaves, but it
> needs that initial connection to know for sure what it's doing.
>

Does it apply to both corosync 1.x and 2.x or only to 2.x with
wait_for_all? Because I actually also was confused about precise
meaning of disabling quorum in pacemaker (setting no-quorum-policy:
ignore). So if I have two node cluster with pacemaker 1.x and corosync
1.x with no-quorum-policy=ignore and no fencing - what happens when
one single node starts?