will have lost quorum, which is not the case with two_node.
> >
> > Are you running with "two_node" in corosync.conf?
> > Are you running with "wait_for_all"? (It's on by default with "two_node")
> >
> > __
Hello,
We recently had an unfortunate sequence on our two-node cluster (nodes n02
and n03) that can be summarized as:
1. n03 became pathologically busy and was STONITHed by n02
2. The heavy load migrated to n02, which also became pathologically busy
3. n03 was rebooted
4. During the startup of
