provider: Lower retry threshold for DNS resolution failures #4459
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a session-wide retry handler that will lower the retry threshold when attempting to contact endpoints that do not exist or if there is a reasonably long DNS resolution issue.
Closes #4457
Closes #3760
Reference #1756
Reference #1354
Previously, the
MaxRetries
default of 25 would mean this RequestError for "no such host" could take upwards of 30 minutes to reveal (I gave up below):Now it will return in a reasonable timeframe:
#3760 case:
#1756 case: