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

Check on connect() for DBClientRS?

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Internal Client, Networking
    • None
    • ALL

      With the change to isAnyNodeOk() in DBClientRS::connect(), we rely on the ReplicaSetMonitorWatcher to keep us up-to-date (if it's stale, our connections will fail). This behavior is different from previous, where we actively checked the replica set again for activity.

      Think if we aren't able to find nodes we know are ok, we should re-check the nodes. A timed backoff may be appropriate as well to avoid spamming reconnect requests.

            Assignee:
            mathias@mongodb.com Mathias Stearn
            Reporter:
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: