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.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47587

repl5.h:
#define MAX_NUM_OF_MASTERS		64

repl5_agmt.c:
typedef struct repl5agmt {
...
	struct changecounter *changecounters[MAX_NUM_OF_MASTERS]; /* changes sent/skipped since server start up */
...
}

cl5_cache.c:
struct clc_buffer {
...
	struct csn_seq_ctrl_block *buf_cscbs [MAX_NUM_OF_MASTERS];
}

Hi,

how to verify this change?

Thanks.

(In reply to Milan Kubík from comment #2)
> Hi,
> 
> how to verify this change?
> 
> Thanks.

Not sure.  Mark worked on this.

Taking steps from bug1031223.

(In reply to Milan Kubík from comment #2)
> Hi,
> 
> how to verify this change?
> 
> Thanks.

Hi Milan, sorry for not getting back to you sooner.

First, I thought Sankar automated this test, so might want to check with him.

To verify it you need to create more than 64 "master" instances and over 64 agreements on one master.  You should be able to just use one of the masters to add the 64+ agreements that point to the other master replica servers - so you don't need 64+ agreements on every master, just one.  Finally, make sure replication works across all the replicas.

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-2014-1385.html