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
attachment 0001-Ticket-48767-flow-control-in-replication-also-blocks.patch
aa64641..ba63658 master -> master commit ba63658 Author: Mark Reynolds mreynolds@redhat.com Date: Mon Jul 11 10:30:04 2016 -0400
d432113..5358b4b 389-ds-base-1.3.4 -> 389-ds-base-1.3.4 commit 5358b4b
Pushed to the remaining branches that have include ticket 47942
ae73aad..2191728 389-ds-base-1.3.3 -> 389-ds-base-1.3.3 commit 2191728
b357e44..11dc556 389-ds-base-1.3.2 -> 389-ds-base-1.3.2 commit 11dc556
1a62647..6dec417 389-ds-base-1.3.1 -> 389-ds-base-1.3.1 commit 6dec417242238791cad12e2420ebb2a1602b8e8f
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1354660
Metadata Update from @mreynolds: - Issue assigned to mreynolds - Issue set to the milestone: 1.3.4.11
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1827
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.