Repeated membership changes from corosync in RHEL 7 Pacemaker Cluster resulting in OOM errors on the nodes
Issue
Corosync is repeatedly experiencing membership updates on one or more nodes, flooding the logs with the following message:
corosync[pid]: [TOTEM ] A new membership (<ip addr>:1844600) was formed. Members
corosync[pid]: [QUORUM] Members[8]: 6 7 1 2 3 4 5 8
corosync[pid]: [MAIN ] Completed service synchronization, ready to provide service.
This coincides with slowly increasing memory consumption eventually resulting in Out of Memory errors in the environment.
Environment
- Red Hat Enterprise Linux 7 w/ High Availability or Resilient Storage
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.