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

XMLWordPrintableJSON

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

      ... 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:
              [DO NOT USE] Backlog - Service Architecture
              Reporter:
              Greg Studer (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: