I implemented DRBD resource level fencing with
crm-unfence-peer.9.sh scripts on both nodes.
Now, I have the following situation on my lab nodes:
resource are running on
- as per
otrs1holds the primary role and
otrs2holds the secondary role
Now when I reboot
otrs2 I get the following message:
Can see that the resources are moved to
If the replication link becomes connected again and DRBD completes its synchronization process, then the constraint is removed. The cluster manager is now free to promote the resource. In fact the constraint is now removed:
But as soon I disable the NIC on
otrs2 (the currently active node) I can see the split-brain occurred:
Obviously this is a split-brain scenario. Why's that so ? is it because
In case of the crm-fence-peer script it is necessary that Pacemakers communication stays available when DRBD’s network link breaks.