#1713 [RFE] Add a task to the SSSD to periodically refresh cached entries
Closed: Fixed None Opened 7 years ago by jhrozek.

This RFE came up during a discussion between Chris Hudson, Simo and me. Some deployments suffer from latency when refreshing a big number of expired entries, for instance during logins that involve refreshing netgroups.

The latency might be mitigated by introducing a new background task that would walk the database periodically and fire a refresh in the background for any entry that is past a threshold


What is the criteria regarding which entries to update? Is it any entry that is old enough or there is also a filter, i.e refresh only: users, groups, services, netgroups, sudo rules, automount maps, SSH data, HBAC, or SELinux mappings?

summary: RFE: Add a task to the SSSD to periodically refresh cached entries => [RFE] Add a task to the SSSD to periodically refresh cached entries
type: defect => enhancement

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11 beta
rhbz: => todo

Fields changed

milestone: SSSD 1.11 beta => SSSD 1.12 beta

There is a customer issue bound to it.

milestone: SSSD 1.12 beta => NEEDS_TRIAGE
selected: =>
_comment0: Analog Devices is the customer.
sssd creates a lag in their lookups.
comes up in weekly call with Analog.
workarounds are difficult to use. => 1360102095601244

Moving to 1.10 and marking as critical as there is a customer demand to see this functionality implemented sooner rather than later.

milestone: NEEDS_TRIAGE => SSSD 1.10 beta

Fields changed

owner: somebody => jhrozek

Fields changed

owner: jhrozek => pbrezina
review: => 0
status: new => assigned

Fields changed

patch: 0 => 1

Fields changed

changelog: => Large deployments may suffer from latency when refreshing a big number of expired entries, for instance during logins that involve refreshing netgroups.
SSSD 1.10 contains a new background task that will periodically search and update all expired cached entries.

resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.10 beta

3 years 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/2755

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.

Metadata