You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When offline, we periodically attempt to contact the remote server to determine if we are back online. This is triggered by a request, which then blocks until the server either responds or we hit the timeout.
It would be nicer behavior if we instead always returned the cache data if we are marked offline at the time the request occurs and instead attempt to reconnect to the remote server out-of-band (similar to the way the midpoint cache works).
This will mean that users won't get intermittent lag in their NSS lookups.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/282
When offline, we periodically attempt to contact the remote server to determine if we are back online. This is triggered by a request, which then blocks until the server either responds or we hit the timeout.
It would be nicer behavior if we instead always returned the cache data if we are marked offline at the time the request occurs and instead attempt to reconnect to the remote server out-of-band (similar to the way the midpoint cache works).
This will mean that users won't get intermittent lag in their NSS lookups.
Comments
Comment from sgallagh at 2009-11-19 22:47:26
Fields changed
status: new => assigned
Comment from sgallagh at 2009-11-23 19:01:18
Fixed in 64e5787
fixedin: => 1.0.0rc
resolution: => fixed
status: assigned => closed
Comment from dpal at 2012-01-19 02:35:40
Fields changed
rhbz: => 0
Comment from sgallagh at 2017-02-24 15:04:48
Metadata Update from @sgallagh:
The text was updated successfully, but these errors were encountered: