#633 Build general mechanism to limit number of parallel LDAP request on the same connection
Closed: wontfix 3 years ago by pbrezina. Opened 13 years ago by simo.

Many servers limit the number of concurrent request a client can make. We should implement checks to avoid getting back errors by inadvertently stepping past this limit.
Ideally we have a core ldap request queuing functionality that will queue requests until a slot opens up.
The queue will also provide means to query if there are free slots before we make a call so that code that explicitly issues parallel requests will know when to stop queuing new requests and wait until the queue is flushed before trying again.

This feature will be used by group processing code that requires multiple parallel requests.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.6.0

Fields changed

priority: major => critical

Fields changed

coverity: =>
milestone: SSSD 1.6.0 => SSSD 1.7.0
upgrade: => 0

Fields changed

cc: => fhanzlik
patch: => 0

Fields changed

milestone: SSSD 1.8.0 => SSSD 1.9.0

Fields changed

blockedby: =>
blocking: =>
milestone: SSSD 1.9.0 => SSSD Deferred
rhbz: =>

Fields changed

rhbz: => 0

Fields changed

design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
priority: critical => minor
selected: =>

Metadata Update from @simo:
- Issue set to the milestone: SSSD Patches welcome

7 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

3 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1675

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.

Login to comment on this ticket.

Metadata