Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: None
Component/s: None
Labels:
None

Server Compat:
- 3.4

It should be possible for a user or operator to set a limit on how stale a member might be before allowing queries.
An extension of this would be to improve driver discovery such that they do not choose a node that is excessively stale, when serving reads

Max staleness spec

depends on

CDRIVER-1363 Implement maxStalenessMS

Closed

CSHARP-1720 Allow users to set a limit on acceptable staleness

Closed

CXX-975 Allow users to set a limit on acceptable staleness

Closed

CXX-976 Allow users to set a limit on acceptable staleness

Closed

JAVA-2248 Allow users to set a limit on acceptable staleness for secondary reads

Closed

NODE-773 Allow users to set a limit on acceptable staleness

Closed

PHPC-752 Allow users to set a limit on acceptable staleness

Closed

PHPLIB-207 Allow users to set a limit on acceptable staleness

Closed

PYTHON-1104 Implement maxStalenessMS

Closed

RUBY-1133 Allow users to set a limit on acceptable staleness

Closed

RUST-33 Allow users to set a limit on acceptable staleness

Closed

is duplicated by

DRIVERS-237 Include replication lag as a method for server selection

Closed

is related to

SERVER-24421 maxStalenessMS support in mongos

Closed

related to

DRIVERS-336 Change "no maxStalenessSeconds" value from 0 to -1

Closed

DRIVERS-335 Update Max Staleness implementation

Closed

(6 depends on, 1 is duplicated by, 1 is related to, 2 related to)

Assignee:: Barrie Segal (Inactive)

Reporter:: Rathi Gnanasekaran (Inactive)

Votes:: 1 Vote for this issue

Watchers:: 7 Start watching this issue

Created:: Mar 01 2016 08:15:33 PM UTC

Updated:: May 27 2022 01:33:26 AM UTC

Resolved:: Oct 19 2016 12:36:20 PM UTC

Start date:: 01/Mar/16

Details

Description

Attachments

Issue Links

Activity

People

Dates