SSSD / sssd

#1717 Limit requests coalescing in time
Closed: Fixed Opened by simo.

Closed: Fixed
Reopen Issue

We have regressed a few times in the code that optimizes out requests by coalescing all identical ones and sending a single request to the provider.
There was no temporal limit to this action so hundreds of requests would pile up indefinitely if no reply would ever come from the provider.
Add a timestamp mechanism to requests so that after a specified timeout an existing request is considered orphaned and is recycled and new requests can be sent to the provider.

Fields changed

owner: somebody => simo
patch: 0 => 1
status: new => assigned
  • master: 185dcb88690f45c7886c95076bd189877aef2289
  • sssd-1-9: dd85581b726d7db264348ae27d77c4615b7f79d0

milestone: NEEDS_TRIAGE => SSSD 1.9.4
resolution: => fixed
status: assigned => closed

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=885078 (Red Hat Enterprise Linux 6)

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=885078 885078]

Metadata Update from @simo:
- Issue assigned to simo
- Issue set to the milestone: SSSD 1.9.4

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/2759

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
None
None
None
Normal
defect
SSSD
1.9.3
0
1
https://bugzilla.redhat.com/show_bug.cgi?id=885078
0
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.