I can reproduce this issue sometimes even with the one and only failover and failback: - Destroy the controller node - Power it up
Watch the split brain as a result, like:
node-3, node-4 reports: Current DC: node-3 (1) - partition with quorum Version: 1.1.10-42f2063 3 Nodes configured 25 Resources configured Online: [ node-3 node-4 ] OFFLINE: [ node-9 ]
vs node-9 reports: Current DC: node-3 (1) - partition with quorum Version: 1.1.10-42f2063 3 Nodes configured 25 Resources configured Online: [ node-3 node-9 ] OFFLINE: [ node-4 ]
I'm not sure if it is a real split brain, or just some pacemaker/corosync issue?
I can reproduce this issue sometimes even with the one and only failover and failback:
- Destroy the controller node
- Power it up
Watch the split brain as a result, like:
node-3, node-4 reports:
Current DC: node-3 (1) - partition with quorum
Version: 1.1.10-42f2063
3 Nodes configured
25 Resources configured
Online: [ node-3 node-4 ]
OFFLINE: [ node-9 ]
vs node-9 reports:
Current DC: node-3 (1) - partition with quorum
Version: 1.1.10-42f2063
3 Nodes configured
25 Resources configured
Online: [ node-3 node-9 ]
OFFLINE: [ node-4 ]
I'm not sure if it is a real split brain, or just some pacemaker/corosync issue?