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

Unified topology never regains nodes which temporarily go down

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.4
    • Affects Version/s: 3.3.3
    • Component/s: None
    • None

      As shown in basic uses of the sdam_viz tool, the unified topology seems to have a serious bug where replset nodes which are lost are not rediscovered when they return to the cluster. This seems to be related to the monitoring loop being disabled since monitoring commands and normal commands both emit error events from the Pool. I also suspect this is highly related to users getting high degree cases of Server selection timed out messages, since selection will necessarily time out if no servers are ever available.

            Assignee:
            matt.broadstone@mongodb.com Matt Broadstone
            Reporter:
            matt.broadstone@mongodb.com Matt Broadstone
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: