-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Server
-
Labels:None
Something like: "When the client knows the primary, it estimates a secondary's staleness each time it checks the secondary by comparing its last write date to the primary's. When there is no primary, the client estimates a secondary's staleness by comparing its last write date to that of the secondary with the most advanced last write date."
- documents
-
SERVER-24421 maxStalenessMS support in mongos
- Closed
-
SERVER-24676 Implement support for maxStalenessMS in the ReplicaSetMonitor
- Closed
-
SERVER-4936 Server support for "maxStalenessMS" read preference option
- Closed
-
SERVER-26927 Update Max Staleness implementation
- Closed
- is documented by
-
SERVER-24675 Add maxStalenessMS to ReadPreferenceSetting
- Closed
- is duplicated by
-
DOCS-8292 Allow users to set a limit on acceptable staleness
- Closed
-
DOCS-9476 Docs for SERVER-24676: Implement support for maxStalenessMS in the ReplicaSetMonitor
- Closed
-
DOCS-9536 Docs for SERVER-24421: maxStalenessMS support in mongos
- Closed
-
DOCS-9544 Docs for SERVER-4936: Server support for "maxStalenessMS" read preference option
- Closed
- is related to
-
DOCS-8197 Add serverSelectionTimeoutMS and heartbeatFrequencyMS to Connection String URI Format
- Closed
- related to
-
SERVER-27346 maxStalenessSeconds doesn't appear in cursor.readPref()
- Closed
-
DOCS-9645 Add maxStalenessSeconds to cursor.readPref
- Closed