Right now, when offline, we wait until we have a client request to try to do a DNS request to resolve servers. In some situation this may lead to wait for a DNS timeout.
DNS resolution could be decoupled from connections and done more frequently when offline increasing online detection chances while also decreasing waits when DNS requests timeouts. When offline requests could be done frequently, while in the online case they would be done only when the DNS entry ttl expires.
Fields changed
coverity: => milestone: SSSD 1.6.0 => NEEDS_TRIAGE upgrade: => 0
owner: somebody => sgallagh
The assertion in the original ticket description is incorrect. We do not wait for DNS resolution until client requests come in. We always attempt to resolve all servers when either the system routing table changes (as reported by netlink) or when the /etc/resolv.conf has been modified.
In either case, this will happen for any significant change in network connectivity, and is NOT deferred until a client request is made. So we feel that there is no significant advantage to polling DNS regularly.
resolution: => wontfix status: new => closed
milestone: NEEDS_TRIAGE => void
Metadata Update from @simo: - Issue assigned to sgallagh - Issue set to the milestone: void
Metadata Update from @jhrozek: - Custom field rhbz adjusted to 0
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/1727
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.