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

Remove from the topology a replica set member whose "me" hostname:port does not match the one that was used to connect to it

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Component/s: None
    • Labels:
      None
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      JAVA-1815 Done 2.13.2, 3.0.2, 3.1.0, 2.14.0
      CSHARP-1283 Done 2.0.1, 2.1
      RUBY-961 Done 2.1.0
      PYTHON-999 Done 3.1
      CDRIVER-1021 Done 1.3.0-rc0
      $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 JAVA-1815 Done 2.13.2, 3.0.2, 3.1.0, 2.14.0 CSHARP-1283 Done 2.0.1, 2.1 RUBY-961 Done 2.1.0 PYTHON-999 Done 3.1 CDRIVER-1021 Done 1.3.0-rc0

      Given the behavior specified in the current version of the SDAM specification, it's possible for get-more/kill-cursor requests to fail in the following scenario:

      • Create MongoClient with a seed list with IP addresses for a replica set with host names as normal DNS names.
      • Execute a query with a non-primary read preference
      • Execute a get-more for that query

      This can happen because server selection will succeed against a seed list host that reports itself as a secondary, but by the time the get-more executes, the primary has identified itself and the driver has replaced all the ip-address-specified seed list hosts with the host names from the primary's server description. The result is that server selection fails for the get-more, as the topology has "forgotten" about the seed list hosts.

      A fix to the SDAM specification has been accepted, and must be implemented in all drivers.

            Assignee:
            barrie Barrie Segal
            Reporter:
            jeff.yemin@mongodb.com Jeffrey Yemin
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: