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.
Bug 1354660 - flow control in replication also blocks receiving results
Summary: flow control in replication also blocks receiving results
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-11 21:43 UTC by Noriko Hosoi
Modified: 2020-09-13 21:42 UTC (History)
4 users (show)

Fixed In Version: 389-ds-base-1.3.5.10-4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 20:44:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1827 0 None None None 2020-09-13 21:42:04 UTC
Red Hat Product Errata RHSA-2016:2594 0 normal SHIPPED_LIVE Moderate: 389-ds-base security, bug fix, and enhancement update 2016-11-03 12:11:08 UTC

Description Noriko Hosoi 2016-07-11 21:43:09 UTC 
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
Comment 2 Sankar Ramalingam 2016-09-15 12:25:22 UTC 
Hi Mark, request you to add steps to verify this bugzilla. Thanks!
Comment 3 mreynolds 2016-09-15 13:23:45 UTC 
(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.
Comment 4 Sankar Ramalingam 2016-09-15 18:32:25 UTC 
(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.
Comment 5 Sankar Ramalingam 2016-09-19 13:56:33 UTC 
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.
Comment 7 errata-xmlrpc 2016-11-03 20:44:03 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.