-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
This supersedes DRIVERS-335. The only part of that ticket which is still relevant is:
- Rename maxStalenessMS to maxStalenessSeconds
These parts of DRIVERS-335 are reverted:
- Parse idleWritePeriodMillis from isMaster, in case a future server version ever includes it (reverted, the idle write period is a 10 second constant you define in your driver code)
- The maxStalenessSeconds can be a float (reverted, it's an integer)
- The smallest value is now heartbeatFrequencyMS + idleWritePeriodMS (superseded, it must now also be at least 90 seconds)
DRIVERS-336 is not superseded, it's still valid: the default value for maxStalenessSeconds is -1, meaning "no max staleness". maxStalenessSeconds=0 is prohibited.
Now, to complete this ticket:
- The smallest value for maxStalenessSeconds is now 90 seconds or heartbeatFrequencyMS + idleWritePeriodMS (10 seconds), whichever is greater.
- Resync Max Staleness JSON tests - they are tagged max-staleness-tests-2016-11-22
- Review Max Staleness prose tests and update your tests
- depends on
-
CDRIVER-1933 Make minimum value of maxStalenessSeconds 90 seconds
- Closed
-
CSHARP-1834 Make minimum value of maxStalenessSeconds 90 seconds
- Closed
-
CXX-1142 Make minimum value of maxStalenessSeconds 90 seconds
- Closed
-
NODE-859 Make minimum value of maxStalenessSeconds 90 seconds
- Closed
-
PYTHON-1192 Make minimum value of maxStalenessSeconds 90 seconds
- Closed
-
RUBY-1178 Make minimum value of maxStalenessSeconds 90 seconds
- Closed
-
RUST-25 Make minimum value of maxStalenessSeconds 90 seconds
- Closed
-
PHPC-827 Update Max Staleness implementation
- Closed
-
JAVA-2389 Make minimum value of maxStalenessSeconds 90 seconds
- Closed
- related to
-
DRIVERS-336 Change "no maxStalenessSeconds" value from 0 to -1
- Closed
-
DRIVERS-335 Update Max Staleness implementation
- Closed