[JAVA-385] Secondary servers in a replication set that are out of date should not be read from Created: 21/Jun/11  Updated: 17/Oct/16  Resolved: 17/Oct/16

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

Type: Improvement Priority: Major - P3
Reporter: Michael D. Norman Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates JAVA-2248 Allow users to set a limit on accepta... Closed

 Description   

We are enabling slaveOK to read from secondary servers, but we have run into many problems with one of our servers that sometimes gets too far behind to be a useful reader. Therefore, the client should not query from any secondary servers that are out of date. Apparently the ability is there for the clients to query from the server, though I'm not sure if there's a way to tell the client to only read from one of the servers: http://www.mongodb.org/display/DOCS/Replica+Set+Internals#ReplicaSetInternals-ReadingfromSecondariesandStaleness



 Comments   
Comment by Jeffrey Yemin [ 17/Oct/16 ]

Closing as duplicate of JAVA-2248

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