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.

Created attachment 597045 [details]
Proposed patch

Description of problem:
Votequorum should register reload callback only once and not after each
change in confdb.

Version-Release number of selected component (if applicable):
Flatiron

How reproducible:
100%

Steps to Reproduce:
1. Load votequorum plugin
2. corosync-objctl -c .usr
3. In log is corosync [VOTEQ ] Reading configuration
4. corosync-objctl -c .usr
5. In log appear another "corosync [VOTEQ ] Reading configuration" this time twice
6. corosync-objctl -c .usr
7. In log appear another "corosync [VOTEQ ] Reading configuration" this time three times
...

Actual results:
Votequorum register reload configuration handler after each change in confdb.

Expected results:
Votequorum register reload configuration handler only once.

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause
Corosync running with votequorum enabled.

Consequence
Votequorum register reload configuration handler after each change in confdb. This will cause in the beginning slow down of corosync and resulting to OOM, ...

Fix
Register callback only at startup

Result
No slowdown, OOM, ...

with this snip in corosync.conf:
quorum {
	provider: corosync_votequorum
}

and debug set to on the following happens:

* corosync-objctl -w quorum.expected_votes
corosync [VOTEQ ] Reading configuration

* corosync-objctl -c qa; corosync-objctl -w qa.test=1
[ nothing from VOTEQ in logs ]

Behaves as expected. corosync-1.4.1-12.el6.x86_64.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0497.html