#3970 Improve dereference threshold handling
Closed: wontfix a year ago by pbrezina. Opened 2 years ago by jhrozek.

This came up in a discussion with Thierry about the performance impact of dereference.

Internally on the DS side, dereferencing a 1000 members creates 1000 SRCHs. This is better if we really want to fetch all 1000 members, but currently SSSD has an absolute threshold.

Instead, Thierry proposed we should have a percent-based threshold to avoid situations like SSSD has 500 out of 1000 members, but the threshold is 10 missing members, so SSSD issues a deref that triggers 1000 SRCHs on the server side instead of doing 500 SRCHs itself.

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Future releases (no date set yet)

2 years ago

Metadata Update from @thalman:
- Issue tagged with: Canditate to close

a year 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)

a year 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/4943

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.