Learn more about these different git repos.
Other Git URLs
be_refresh periodically updates expired records (currently only netgroups). If we get to the point when too many records are expired, we may decrease backend throughput.
We should implement some throttling, ideally based on real customer data. For example: update records in bursts and force some delay between individual bursts.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.11 beta summary: ammend be_refresh with some throttling ability => [RFE] ammend be_refresh with some throttling ability type: defect => enhancement
rhbz: => 0
Moving open tickets from 1.11 beta to 1.11 beta2
milestone: SSSD 1.11 beta => SSSD 1.11 beta 2
changelog: => milestone: SSSD 1.11 beta 2 => NEEDS_TRIAGE
milestone: NEEDS_TRIAGE => Interim Bucket
milestone: Interim Bucket => SSSD 1.12 beta
milestone: SSSD 1.12 beta => SSSD 1.13 beta
mark: => 0
So far no throttling was required, let's reconsider when we implement the full be_refresh for other types as well.
milestone: SSSD 1.13 beta => SSSD 1.13 backlog priority: major => critical
So far no throttling was required, let's lower the priority per PavelB's suggestion and see if we are required to implement one..
priority: critical => minor
Mass-moving tickets not planned for the next two releases.
Please reply with a comment if you disagree about the move..
milestone: SSSD 1.13 backlog => SSSD 1.15 beta
I would defer.
review: 0 => 1 selected: => Not need sensitive: => 0
Since this enhancement was not needed or implemented in 4 years, I'm closing this ticket.
resolution: => wontfix status: new => closed
Metadata Update from @pbrezina: - Issue set to the milestone: SSSD Future releases (no date set yet)
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/2983
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.