nodejs driver - reconnect slow when PRIMARY GOES DOWN

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Environment:
      mongodb@2.2.25
      npm: 3.10.10
      nodejs: v6.10.0
      OS: xenial
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      I want to know how does nodejs driver behave when PRIMARY GOES DOWN.
      Issue db.shutdownServer() on Primary
      "SECONDARY" become Primary right away.

      But driver takes at least 11 second hanging before issuing another write command again.

      I test with various number for connectTimeoutMS & socketTimeoutMS & haInterval
      But it does not help.

      Connection String:

      "mongodb://xxx:xxx@1.10.21.67:27017,1.10.21.98:27017/test?replicaSet=hhawsmongo&poolSize=1&autoReconnect=true&reconnectTries=100&connectTimeoutMS=1000&socketTimeoutMS=1000&haInterval=500&forceServerObjectId=true"

              Assignee:
              Matt Broadstone
              Reporter:
              Aung
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: