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

Client hangs on reconnect when partitioned from majority of replset

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • 3.0.1
    • None
    • Core
    • None

    Description

      See Linked issue. User is running a setup with 4 docker instances:

      3 Docker DBs:

      • Host 1 member of Replicaset
      • Runs a js script that
      • Hosts an express server with meta info
      • Attempts multiple rapid connections, reads, and writes
        1 Docker Client:
      • Runs script that:
      • pings each express server on DB for results
      • aggregates results into metadata

      It appears that the bug is as follows: when a member node is partitioned from the network, the script running on that node loses its connection to the replicaset, as expected. However, when the node rejoins the network, the `MongoClient.prototype.connect` promise never settles, neither resolving or rejecting.

      The express server continues to operate.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. NODE-1363 Unable to establish a connection to a MongoDB cluster after a connection between Primary and its peers was disrupted and then fixed

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. NODE-1340 Reconnecting to Mongos proxy server never fires the reconnect event

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. NODE-1363 Unable to establish a connection to a MongoDB cluster after a connection between Primary and its peers was disrupted and then fixed

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              daniel.aprahamian@mongodb.com Daniel Aprahamian (Inactive)
              daniel.aprahamian@mongodb.com Daniel Aprahamian (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: