Learn more about these different git repos.
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.
owner: somebody => simo
patch: 0 => 1
status: new => assigned
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
to comment on this ticket.