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

SDAM Refactor

    XMLWordPrintableJSON

Details

    • Epic
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • None
    • None
    • None
    • Hide

      2018-08-14 : Initial target 2018-09-14 (4weeks)

      2018-09-18 : Updated target date 2018-09-21 (5weeks)
      Waiting on code review for the last 2 tickets.

      Show
      2018-08-14 : Initial target 2018-09-14 (4weeks) 2018-09-18 : Updated target date 2018-09-21 (5weeks) Waiting on code review for the last 2 tickets.

    Description

      We have massive duplication when it comes to topologies in the node driver. Presently there are three types: Server, Mongos, and ReplSet. Mongos and ReplSet are both containers of Server instances, with ReplSet implementing SDAM and Mongos implementing its own custom round-robin selector. The SDAM spec actually allows us to represent all three types of topologies with a single type + description, so we should do that! Initial estimates are that this could remove ~5-6k loc between the two projects.

      Attachments

        Issue Links

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. NODE-1054 Error "Cannot read property 'wireProtocolHandler' of null" when server is not ready

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

          Bug - A problem which impairs or prevents the functions of the product. NODE-1140 Rapid Increase in Connections Causes Severe Performance Degradation

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

          Bug - A problem which impairs or prevents the functions of the product. NODE-1166 Failure to reconnect through mongos after abrupt replicaset primary failure

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

          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

          Bug - A problem which impairs or prevents the functions of the product. NODE-1388 Oplog Tailing Stalls during MongoDB Failover

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

          Bug - A problem which impairs or prevents the functions of the product. NODE-1395 connect fails silently and intermittently when connecting to MongoDB version 3.0.8

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

          Bug - A problem which impairs or prevents the functions of the product. NODE-1475 MongoClient failed to connect to server on first connect, but connects later

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

          Bug - A problem which impairs or prevents the functions of the product. NODE-1318 Authentication attempts against arbiter node

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          related to

          Task - A task that needs to be done. NODE-1851 mongoClient.connect hangs sometimes and don't call the callback

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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved:
                5 weeks, 3 days