[DRIVERS-327] SDAM spec update : Update the topology from each handshake Created: 29/Sep/16  Updated: 17/Jun/20  Resolved: 23/Feb/18

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Rathi Gnanasekaran Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on CDRIVER-562 cluster should send newly-run ismaste... Closed
depends on JAVA-2372 SDAM spec update : Update the topolog... Closed
depends on PYTHON-1163 If client runs an ismaster for a serv... Closed
depends on CSHARP-1814 SDAM spec update : Update the topolog... Closed
depends on CXX-1107 SDAM spec update : Update the topolog... Closed
depends on CXX-1108 SDAM spec update : Update the topolog... Closed
depends on NODE-841 SDAM spec update : Update the topolog... Closed
depends on PHPC-824 SDAM spec update : Update the topolog... Closed
depends on RUBY-1166 SDAM spec update : Update the topolog... Closed
Related
Driver Compliance:
Key Status/Resolution FixVersion
PYTHON-1163 Won't Fix
CDRIVER-562 Done 1.5.0
SCALA-275 Done
RUBY-1166 Won't Fix 12_01_17
NODE-841 Done
CSHARP-1814 Won't Fix
CXX-1108 Done
PERL-672 Won't Fix
JAVA-2372 Won't Fix
PHPC-824 Done 1.2.0
CXX-1107 Won't Fix

 Description   

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.


Generated at Thu Feb 08 08:21:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.