RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
the corosync memory leaks when the peer node stop/start/restart

Version-Release number of selected component (if applicable):
corosync-1.4.6
REHL6.0

How reproducible:
create one cluster, let one or more members stop/start/restart
then `ps auxf | grep corosync` you will find that the memory is increaments 
every time the other nodes stop/start/restart 

e.g
NODEA
while [ 1 ];do /etc/init.d/corosync restart;done; 

NODEB
ps auxf | grep corosync 

in NODEB, you will find the memory increaments very fast and will not down forever.

Steps to Reproduce:
1. make two nodes cluster
2. let one node stop/start/restart
3. `ps -auxf | grep corosync` to see the node which not stop/start/restart 


Actual results:
the memory which consumed by corosync increaments very fast!

Expected results:
the memory will not leak

Additional info:

Youyun,
can you please attach corosync.conf? Are there any services using corosync running or it's pure corosync start/stop test? If so, are you sure corosync will really never stop eating memory (so every restart means new allocated memory)? Because if it's not so, it's not a bug (there are structures, which may be filled during lifetime of corosync but they are limited in size).

Also 6.5 capacity is constrained so moving to 6.6.

Youyun,
can you please attach additional files/provide additional informations I've asked in Aug? Otherwise I will probably close this bug, because I'm unable to reproduce it.

Thanks,
  Honza

Youyun,
any news?

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days