You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1717
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.
Comments
Comment from simo at 2012-12-14 22:09:52
Fields changed
owner: somebody => simo
patch: 0 => 1
status: new => assigned
Comment from jhrozek at 2012-12-18 18:55:16
milestone: NEEDS_TRIAGE => SSSD 1.9.4
resolution: => fixed
status: assigned => closed
Comment from jhrozek at 2012-12-18 18:59:08
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]
Comment from simo at 2017-02-24 14:29:40
Metadata Update from @Simo:
The text was updated successfully, but these errors were encountered: