Hide Forgot
This bug is created as a clone of upstream ticket: https://fedorahosted.org/389/ticket/48767 In ticket 47942 a flow control was introduced to reduce the load of a replication consume. It adds some pauses in the asynch sending of updates. Unfortunately while it pauses it holds the reader lock, so that the result reader thread is also paused
Hi Mark, request you to add steps to verify this bugzilla. Thanks!
(In reply to Sankar Ramalingam from comment #2) > Hi Mark, request you to add steps to verify this bugzilla. Thanks! There is nothing to verify. This "fix" is a potential performance improvement in replication, and nothing else. I suppose the only thing to verify is if replication still works.
(In reply to mreynolds from comment #3) > (In reply to Sankar Ramalingam from comment #2) > > Hi Mark, request you to add steps to verify this bugzilla. Thanks! > > There is nothing to verify. This "fix" is a potential performance > improvement in replication, and nothing else. I suppose the only thing to > verify is if replication still works. Thanks Mark!. I will check reliab15 results + dsReplication tier1/2/3 tests and then mark it as Verified.
1. Reliab15 test results seems to be good with the latest build of 389-ds-base-1.3.5.10-11 build. 2. I didn't observe any issues with replication so far with my testing. 3. No regression or failures reported from MMR tests in TET acceptance. Based on above, I am marking the bug as Verified.
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. https://rhn.redhat.com/errata/RHSA-2016-2594.html