Delaying Fencing in a Two Node Cluster to Prevent Fence Races or "Fence Death" Scenarios

Solution Verified - Updated -

Issue

  • How can I avoid fence races or fence death scenarios when both nodes detect a token loss?
  • How can I resolve a one-time fencing race without a quorum disk in two node clusters?
  • My two node cluster turned itself off.
  • Two Nodes fencing each other.
  • Adding delay attribute in fencing agent

Environment

  • Red Hat Enterprise Linux (RHEL) 5 Update 6 or later (with the High Availability Add-On)
  • Red Hat Enterprise Linux (RHEL) 6 Update 1 or later (with the High Availability Add-On)
  • Red Hat Enterprise Linux (RHEL) 7 (with the High Availability Add-On)
  • Red Hat Enterprise Linux (RHEL) 8 (with the High Availability Add-On)
  • Two-node High Availability cluster
    • While a delay can be used for various purposes, it is typically only needed in environments where those nodes can race to fence. This generally only occurs if the fence device is accessed over a separate network interface than that which is used for cluster communications.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content