Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-6610

all nodes in the seed string of DBClientRS are considered unhidden until proven otherwise

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
    • Service Arch
    • ALL

      ... this means when we first connect to the hosts, and potentially on reconnect, we'll potentially start reading from hidden secondaries until the monitoring thread forces a check.

      Solution is probably to pass the information from the isMaster call in _checkConnection to the creation of the new Node.

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: