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

Incorrect removal of Unknown server type from ReplicaSetNoPrimary topology

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.3.2
    • Fix Version/s: 3.3.4
    • Component/s: core
    • Labels:
      None
    • Environment:
      Using NodeJS driver directly in Node v12.3.1
    • MongoDB Version:
      4.2.0

      Description

      I apologize if this is not a bug and merely a misunderstanding of the spec/implementation on my part, but I am hoping to at least get clarification on a possible inconsistency I have noticed while doing some chaos testing against a replicaSet.

      According to this table in the SDAM spec , when a topology of type ReplicaSetNoPrimary receives a server of type Unknown the driver should update the description and do nothing. However, in lib/core/sdam/topology_description.js#L192|https://github.com/mongodb/node-mongodb-native/blob/next/lib/core/sdam/topology_description.js#L192] it appears that the driver opts to remove Unknown servers from the topology description. 

       

        Attachments

          Activity

            People

            Assignee:
            matt.broadstone Matt Broadstone
            Reporter:
            brian@finbox.com Brian Dentino
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: