Odd cluster membership changes in HAE cluster

This document (7015215) 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
SUSE Linux Enterprise Server 10

Situation

Unexpected cluster membership changes are taking place in the HAE cluster.
The cluster totem section of /etc/corosync/corosync.conf shows the following:


totem {
#--snip--
    token:      30000
    consensus:   6000
#--snip--
}

Resolution

1. Change the consensus value to 36000 or more. The new /etc/corosync/corosync.conf file should look like this:

totem {
#--snip--
    token:      30000
    consensus:  36000
#--snip--
}

2. Copy the modified /etc/corosync/corosync.conf file to ALL other nodes in the cluster.
3. Run /etc/init.d/openais stop on all but one node.
4. Run /etc/init.d/openais restart on the final node.
5. Run /etc/init.d/openais start on all remaining nodes.

Cause

Invalid consensus value. Per the corosync.conf(5) man page, the consensus value should be a minimum of 1.2 times the token value. Since the fix requires changing the main cluster configuration file, the entire cluster must be restarted.

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:7015215
Creation Date: 17-Jun-2014
Modified Date:14-Oct-2022
- 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