#1885 Use a shorter retry timeout for SRV queries in cases the query cannot be resolved (negative timeout)
Closed: Fixed None Opened 6 years ago by jhrozek.

The retry time to resolve a SRV query again is the same for cases where the SRV resolution works fine and for cases where it doesn't. That's wrong I think, we should set a shorter retry interval for cases where the lookup fails. Typically this would not be a problem because the SSSD can either stick to the server that works or if none work, the client is usually really offline and going online (as a result of libnl callback) would reset the status.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11 beta

Re-test as it might have been fixed by some other patch.

changelog: =>
milestone: SSSD 1.13 beta => Interim Bucket

Fields changed

milestone: Interim Bucket => SSSD 1.12 beta

Fields changed

owner: somebody => preichl

Fields changed

patch: 0 => 1

resolution: => fixed
status: new => closed

Metadata Update from @jhrozek:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.12 beta

2 years ago

Login to comment on this ticket.

Metadata