-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
First implementation for DRIVERS-2757.
Use Case
As a... Node.js driver user
I want... DNS lookup failures to be retried automatically on the driver side
So that... I don't have to build retry logic into my application
User Experience
- Less frequent connection failure errors
Dependencies
- None
Risks/Unknowns
- What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
- Which actual errors should we retry? Only transient ones or all?
- https://nodejs.org/api/dns.html#error-codes
- Check to find out what the error codes mean
- Is there an opportunity to improve existing documentation on this subject?
Acceptance Criteria
Implementation Requirements
- Retry the initial srv txt lookups once on failure (TBD which specific errors)
Testing Requirements
- unit test, spec test sync, etc
- Note: try to write the testing in a way that is potentially adaptable as a general drivers prose test
Documentation Requirements
- DOCSP ticket, API docs, etc
Follow Up Requirements
- N/A, DRIVERS-2757 is the follow up
- is depended on by
-
DRIVERS-2757 Retry on DNS failure
- Backlog
- is related to
-
NODE-6129 Retry on DNS failure
- Blocked