389-ds-base

#48767 flow control in replication also blocks receiving results
Closed: wontfix Opened by lkrispen.

Closed: wontfix
Reopen Issue

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

aa64641..ba63658 master -> master
commit ba636587e77423c7773df60894344dea0377c36f
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 5358b4babeed487fd0878fda0928ad76a3727174

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 21917289be4ff34b6f2ad392b083267af5983cbc

b357e44..11dc556 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit 11dc5565ea60dbb5fe4787c0d96c2392394acf14

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.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)
Metadata
None
None
None
Normal
ack
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.