Learn more about these different git repos.
Other Git URLs
Currently there is one timeout option we pass to c-ares. However, that option is per-nameserver. I guess that makes sense from a resolver library POV - as a resolver library you want to control how long you talk to each name server.
We have been mostly OK with this because in most situations the resolver can't connect the socket to the name server at all at times out immediatelly. Problems arise when the server is very slow to respond, drops packets.
To solve this in SSSD we need to have control over how long a name resolution takes regardless of the number of name servers and also regardless of the number of servers in failover.
The failover in SSSD has the concept of "services". LDAP is a service, Kerberos is a service etc. From back end you don't care and don't know how many servers there are in a service. From fail over we don't know and don't care how many name servers there are.
My proposal is to:
- change the current "dns_resolver_timeout" to be per-service, so the semantics would be "How long to wait until we get an LDAP server IP address" for example
- introduce a new option, something like "dns_resolver_server_timeout", that would control a per-server timeout. This option could maybe be undocumented, it seems quite low-level.
- hide the per-nameserver resolver timeout (only #define it). It is too low level.
milestone: NEEDS_TRIAGE => SSSD 1.7.0
owner: somebody => jhrozek
summary: Improve handling of DNS timeout => [RFE] Improve handling of DNS timeout
type: defect => enhancement
status: new => assigned
patch: 0 => 1
resolution: => fixed
status: assigned => closed
rhbz: => 0
rhbz: 0 => [https://bugzilla.redhat.com/show_bug.cgi?id=726467 726467]
Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.7.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:
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.
to comment on this ticket.