Perform server selection for sessions check if required

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.3.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      From the driver-sessions specification:

      If the TopologyDescription and connection type indicate that
      the driver is not connected to any servers, OR
      is not a direct connection AND is not connected to a data-bearing server
      then a driver must do a server selection for any server whose type is data-bearing. Server selection will either time out or result in a TopologyDescription that includes at least one connected, data-bearing server.

      We do not do this, which is leading to errors when running the sessions YAML tests. Specifically, there a failCommand is causing the primary to transition to Unknown so our synchronous check for logicalSessionsTimeoutMinutes fails due to being temporarily null (until the server selection for the next operation).

              Assignee:
              Matt Broadstone
              Reporter:
              Matt Broadstone
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: