-
Type: Epic
-
Resolution: Fixed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Done
-
SDAM Refactor
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.
- is depended on by
-
NODE-1054 Error "Cannot read property 'wireProtocolHandler' of null" when server is not ready
- Closed
-
NODE-1140 Rapid Increase in Connections Causes Severe Performance Degradation
- Closed
-
NODE-1166 Failure to reconnect through mongos after abrupt replicaset primary failure
- Closed
-
NODE-1340 Reconnecting to Mongos proxy server never fires the reconnect event
- Closed
-
NODE-1363 Unable to establish a connection to a MongoDB cluster after a connection between Primary and its peers was disrupted and then fixed
- Closed
-
NODE-1388 Oplog Tailing Stalls during MongoDB Failover
- Closed
-
NODE-1395 connect fails silently and intermittently when connecting to MongoDB version 3.0.8
- Closed
-
NODE-1475 MongoClient failed to connect to server on first connect, but connects later
- Closed
-
NODE-1318 Authentication attempts against arbiter node
- Closed
- related to
-
NODE-1851 mongoClient.connect hangs sometimes and don't call the callback
- Closed