HAE no quorum policy for various numbers of nodes

This document (7012110) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise High Availability Extension 11 (HAE)
SUSE Linux Enterprise Server 11 (SLES)

Situation

The cluster does not behave as expected when there is no quorum.

A two node cluster has a no-quorum-policy of stop.


# cibadmin -Q --scope crm_config | grep no-quorum-policy
<nvpair id="cib-bootstrap-options-no-quorum-policy" name="no-quorum-policy" value="stop"/>

A three node cluster with OCFS2 volume resources has a no-quorum-policy of ignore


# cibadmin -Q --scope crm_config | grep no-quorum-policy
<nvpair id="cib-bootstrap-options-no-quorum-policy" name="no-quorum-policy" value="ignore"/>

Resolution

Configure the no-quorum-policy for two node clusters to ignore.
# crm configure property no-quorum-policy=ignore

NOTE: Do not set no-quorum-policy=ignore on two node HAE12 clusters. This recommendation is for SLES11 only. HAE12 two node clusters should remain no-quorum-policy=stop.

Configure the no-quorum-policy for three nodes or more with OCFS2 volume resources to freeze.
# crm configure property no-quorum-policy=freeze

Configure the no-quorum-policy for three nodes or more without OCFS2 volume resources to anything but NONE. Most customers choose "ignore" in this configuration.
# crm configure property no-quorum-policy=ignore

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

Document ID:7012110
Creation Date: 09-Apr-2013
Modified Date:03-Mar-2020
- SUSE Linux Enterprise High Availability Extension
- SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com