Repeated membership changes from corosync in RHEL 7 Pacemaker Cluster resulting in OOM errors on the nodes

Solution Verified - Updated -

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, 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