-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
In scope of SPEC-1176, the following prose was added to the SDAM specification:
Note: Server description for each server MUST be updated (replaced) every heartbeat. However, new description MUST NOT cause the SDAM flow to be executed if the new description is equal, as defined in this section, to the previous description
However, the SDAM flow must be executed for each received ismaster response to correctly maintain the topology view.
https://github.com/mongodb/specifications/commit/5d5946e7134f005c5aa715ef60f02fe0207673da
- depends on
-
CDRIVER-3555 Drivers must run SDAM flow even when server description is equal to the last one
- Closed
-
CXX-1950 Drivers must run SDAM flow even when server description is equal to the last one
- Closed
-
MOTOR-508 Drivers must run SDAM flow even when server description is equal to the last one
- Closed
-
PHPC-1564 Drivers must run SDAM flow even when server description is equal to the last one
- Closed
-
PYTHON-2145 Drivers must run SDAM flow even when server description is equal to the last one
- Closed
-
GODRIVER-1511 Drivers must run SDAM flow even when server description is equal to the last one
- Closed
-
JAVA-3642 Drivers must run SDAM flow even when server description is equal to the last one
- Closed
- is related to
-
CSHARP-3012 Remove a server from a multiServercluster in case if the server is not valid for the current cluster
- Closed
- related to
-
DRIVERS-760 Add SDAM test for debouncing topology description updates
- Implementing