Hey all,
From what I see in the documentation for fabric fencing, Pacemaker requires an administrator to login to the node to manually start and unfence the node after some failure.
https://clusterlabs.org/pacemaker/doc/deprecated/en-US/Pacemaker/2.0/html/Pacemaker_Explained/s-unfencing.html
The concern I have is if there is an intermittent network issues, a node may get fenced and we have to wait for someone to log into the cluster and bring the node back online. Meanwhile the network issue may have resolved itself shortly after the node was fenced.
From what I see in the documentation for fabric fencing, Pacemaker requires an administrator to login to the node to manually start and unfence the node after some failure.
https://clusterlabs.org/pacemaker/doc/deprecated/en-US/Pacemaker/2.0/html/Pacemaker_Explained/s-unfencing.html
The concern I have is if there is an intermittent network issues, a node may get fenced and we have to wait for someone to log into the cluster and bring the node back online. Meanwhile the network issue may have resolved itself shortly after the node was fenced.
I wonder if there are any configurations or popular solutions that people use to automatically unfence nodes and have them rejoin the cluster?
Gerry Sommerville
E-mail: ge...@ca.ibm.com
_______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
