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

Make reconfig() in rslib.js resilient to NodeNotFound error

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.6.3, 3.7.1
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v3.6
    • Repl 2017-12-04
    • 0

    Description

      If the connections used for heartbeats get closed on the node, reconfig command will return an error like the following. reconfig() is only used for testing and should be resilient to this error.

      {
        "ok" : 0,
        "errmsg" : "Quorum check failed because not enough voting nodes responded; required 2 but only the following 1 voting nodes responded: ip-10-187-92-235:21010; the following nodes did not respond affirmatively: ip-10-187-92-235:21011 failed with End of file, ip-10-187-92-235:21012 failed with End of file",
        "code" : 74,
        "codeName" : "NodeNotFound",
        ...
      }
      

      Attachments

        Issue Links

          Activity

            People

              siyuan.zhou@mongodb.com Siyuan Zhou
              siyuan.zhou@mongodb.com Siyuan Zhou
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: