Can I configure pacemaker to continue to manage resources after a loss of quorum in RHEL 6, 7, 8 or 9 ?
Environment
- Red Hat Enterprise Linux (RHEL) 6, 7, 8 or 9 with the High Availability Add On
pacemaker
Issue
- Can I configure pacemaker to continue to manage resources after a loss of quorum?
- How do I use the
no-quorum-policyattribute?
Resolution
IMPORTANT : Red Hat does not support management of cluster resources in a cluster partition that does not have quorum, thus the no-quorum-policy pacemaker property should not be set to ignore.
RHEL 6
`no-quorum-policy` should not be set to `ignore` in two-node clusters in RHEL 6, as `cman` is the quorum-provider in this release, and it allows one node to remain quorate as long as `
RHEL 7, 8 and 9
`no-quorum-policy` should not be set to `ignore`, as [`votequorum`'s `two_node` mode and `auto_tie_breaker` mode](https://access.redhat.com/solutions/1293523) can be used instead of ignoring quorum for two-node clusters, or `auto_tie_breaker` and/or `last_man_standing` can be used in larger clusters.
To reset no-quorum-policy attribute to default cluster setting use the command below.
# pcs property unset no-quorum-policy
Root Cause
pacemaker offers an attribute called no-quorum-policy which allows an administrator to configure the cluster to allow nodes to continue managing resources even after they have lost quorum. Red Hat does not recommend or support doing so.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.