#1719 [RFE] Improve offline mode performance
Closed: cloned-to-github 3 years ago by pbrezina. Opened 11 years ago by prefect.

When running in offline mode with a network connection but uncontactable kerberos and ldap servers, sssd currently introduces long pauses while trying to repeatedly discover whether or not the remote servers have recovered. These delays disappear while sssd believes the servers to be offline, but then sssd will check if the service has come up periodically, reintroducing the delay, making sssd unusable in this situation. This may occur where directory servers are only accessible within a company firewall for example.

This checking should be done in the background such that the user is unaware of any delays. For a machine that's typically away from the authentication servers (laptop) it may also be useful to be able to set a preference that the machine is assumed to be offline until servers are discovered, to avoid any initial delay.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11 beta
priority: minor => major
summary: Improve offline mode performance => [RFE] Improve offline mode performance

Fields changed

rhbz: => todo

Fields changed

milestone: SSSD 1.11 beta => SSSD 1.12 beta

I think the offline_timeout parameter helps this use-case in the short term. Unfortunately, we don't have the capacity to do more in 1.14..

changelog: =>
mark: => 0
milestone: SSSD 1.14 beta => SSSD 1.15 beta
review: => 0
selected: =>
sensitive: => 0

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

7 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/2761

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.

Metadata Update from @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata