-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
Multi-threaded drivers should evaluate whether they can or should use ismaster responses from regular connection handshakes to update their topology info, the same as they use ismaster responses on monitoring sockets now.
Update to SDAM spec :
https://github.com/mongodb/specifications/commit/34de1f2ebb3945d5da3b36973c0de58423dae8b2
Note the spec says that multi-threaded drivers SHOULD use this information in order to respond faster to topology changes, but the spec does not say you MUST do so.
- depends on
-
CDRIVER-562 cluster should send newly-run ismasters through SDAM machinery
- Closed
-
JAVA-2372 SDAM spec update : Update the topology from each handshake
- Closed
-
PYTHON-1163 If client runs an ismaster for a server, it should update the topology
- Closed
-
CSHARP-1814 SDAM spec update : Update the topology from each handshake
- Closed
-
CXX-1107 SDAM spec update : Update the topology from each handshake
- Closed
-
CXX-1108 SDAM spec update : Update the topology from each handshake
- Closed
-
NODE-841 SDAM spec update : Update the topology from each handshake
- Closed
-
PHPC-824 SDAM spec update : Update the topology from each handshake
- Closed
-
RUBY-1166 SDAM spec update : Update the topology from each handshake
- Closed