[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: |
|
||||||||||||||||||||||||
| 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: The driver estimates the staleness of each secondary, based on lastWriteDate values provided in server isMaster responses, |