With votequorum's last_man_standing enabled, the last node still loses quorum when the second-to-last node becomes unresponsive in a RHEL 7 High Availability cluster

Solution Verified - Updated -

Issue

  • I have last_man_standing configured in this cluster, nodes are removed one-by-one in a cascading fashion, and the number of votes required for quorum is decreased after each event. However when the cluster membership is down to the last two nodes and one of them leaves, the remaining node loses quorum.
  • last_man_standing doesn't work when the last node leaves.
  • Is last_man_standing supposed to work all the way down to a single node?

Environment

  • Red Hat Enterprise Linux 7 (with the High Availability Add-on)
  • Red Hat Enterprise Linux 8 (with the High Availability Add-on)
  • corosync with the votequorum service

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