https://lists.clusterlabs.org/pipermail/users/2021-August/029584.html
Your message is a word for word duplicate of the linked email. On Tue, Aug 31, 2021 at 6:47 PM Kiril Pashin <kir...@ca.ibm.com> wrote: > > Hi , > > 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/solutions that people use to > automatically unfence nodes? > Is there a reason Pacemaker doesn't allow nodes to automatically be unfenced > / rejoin the cluster? > > Kiril Pashin > DB2 Purescale Development & Support > kir...@ca.ibm.com > > > > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
