[JAVA-2248] Allow users to set a limit on acceptable staleness for secondary reads Created: 15/Jul/16  Updated: 19/Oct/16  Resolved: 27/Jul/16

Status: Closed
Project: Java Driver
Component/s: Cluster Management
Affects Version/s: None
Fix Version/s: 3.4.0

Type: New Feature Priority: Major - P3
Reporter: Jeffrey Yemin Assignee: Jeffrey Yemin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by DRIVERS-293 Allow users to set a limit on accepta... Closed
Duplicate
is duplicated by JAVA-385 Secondary servers in a replication se... Closed
Related
is related to JAVA-309 when choosing slave to read from, sho... Closed
Epic Link: MongoDB 3.4 for Java driver

 Description   

Improve replica set server selection for secondary reads such that a secondary that is behind the primary by more than a user-specified limit will be excluded.



 Comments   
Comment by Githook User [ 27/Jul/16 ]

Author:

{u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}

Message: JAVA-2248: Read preference gains a new option: maximum staleness.

The driver estimates the staleness of each secondary, based on lastWriteDate values provided in server isMaster responses,
and select only those secondaries whose staleness is less than or equal to the maximum configured staleness.
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/69078736a625cb21d27dc02fbb0c6211eba42d7d

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