Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-2421

Drivers should include topology description in server selection timeout errors

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • Server Selection
    • None
    • Needed
    • Hide

      NA

      Show
      NA
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      CDRIVER-4614 In Code Review
      CXX-2675 Backlog
      CSHARP-4613 Works as Designed
      GODRIVER-2809 Done
      JAVA-4935 Works as Designed
      NODE-5196 Works as Designed
      MOTOR-1119 Duplicate
      PYTHON-3667 Duplicate 3.11
      PHPC-2254 Blocked
      RUBY-3240 Works as Designed
      RUST-1630 Works as Designed
      $i18n.getText("admin.common.words.show")
      #scriptField, #scriptField *{ border: 1px solid black; } #scriptField{ border-collapse: collapse; } #scriptField td { text-align: center; /* Center-align text in table cells */ } #scriptField td.key { text-align: left; /* Left-align text in the Key column */ } #scriptField a { text-decoration: none; /* Remove underlines from links */ border: none; /* Remove border from links */ } /* Add green background color to cells with FixVersion */ #scriptField td.hasFixVersion { background-color: #00FF00; /* Green color code */ } /* Center-align the first row headers */ #scriptField th { text-align: center; } Key Status/Resolution FixVersion CDRIVER-4614 In Code Review CXX-2675 Backlog CSHARP-4613 Works as Designed GODRIVER-2809 Done JAVA-4935 Works as Designed NODE-5196 Works as Designed MOTOR-1119 Duplicate PYTHON-3667 Duplicate 3.11 PHPC-2254 Blocked RUBY-3240 Works as Designed RUST-1630 Works as Designed

    Description

      Summary

      Drivers that do not already include the topology description in server selection timeout error messages should do so. Some drivers do this already, e.g. Python (see PYTHON-2136) and Ruby, and have found it useful.

      Motivation

      Who is the affected end user?

      Users who are encountering server selection timeout errors.

      How does this affect the end user?

      Currently it can be hard for them or us to tell what the driver's view of their topology is, making it hard to diagnose why server selection is failing.

      How likely is it that this problem or use case will occur?

      This is likely to impact anyone who is encountering server selection timeout errors, which are fairly common. Users often encounter these while trying to connect to a new cluster, write a new application, when their cluster gets in an unhealthy state, etc.

      If the problem does occur, what are the consequences and how severe are they?

      The user has difficulty debugging and fixing the problem.

      Is this issue urgent?

      No.

      Is this ticket required by a downstream team?

      No, but it would help users of downstream tools like mongosh if the Node driver doesn't include this information already.

      Is this ticket only for tests?

      No, functional changes are needed.

      Attachments

        Activity

          People

            Unassigned Unassigned
            kaitlin.mahar@mongodb.com Kaitlin Mahar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: