Build general mechanism to limit number of parallel LDAP request on the same connection

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/633

• Created at 2010-09-28 16:29:57 by simo
• Closed at 2020-03-24 14:23:01 as wontfix
• Assigned to nobody

---

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.

Comments

---

Comment from dpal at 2010-10-14 15:27:02

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.6.0

---

Comment from dpal at 2010-10-14 15:27:17

Fields changed

priority: major => critical

---

Comment from dpal at 2011-02-03 15:27:37

Fields changed

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

---

Comment from sgallagh at 2011-05-05 01:56:50

Fields changed

cc: => fhanzlik
patch: => 0

---

Comment from dpal at 2011-07-22 21:40:44

Fields changed

milestone: SSSD 1.8.0 => SSSD 1.9.0

---

Comment from dpal at 2012-01-16 16:27:47

Fields changed

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

---

Comment from dpal at 2012-01-19 03:19:33

Fields changed

rhbz: => 0

---

Comment from arubin at 2013-01-03 16:35:13

Fields changed

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

---

Comment from simo at 2017-02-24 14:40:37

Metadata Update from @Simo:

• Issue set to the milestone: SSSD Patches welcome

---

Comment from pbrezina at 2020-03-24 14:23:00

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.

---

Comment from pbrezina at 2020-03-24 14:23:02

Metadata Update from @pbrezina:

• Issue close_status updated to: wontfix
• Issue status updated to: Closed (was: Open)