Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-6451

Implement retry on DNS failure

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      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?
      • 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

            Assignee:
            Unassigned Unassigned
            Reporter:
            daria.pardue@mongodb.com Daria Pardue
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: