Incorrect removal of Unknown server type from ReplicaSetNoPrimary topology

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.3.4
    • Affects Version/s: 3.3.2
    • Component/s: Core
    • Environment:
      Using NodeJS driver directly in Node v12.3.1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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. 

       

              Assignee:
              Matt Broadstone
              Reporter:
              Brian Dentino
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: