[JAVA-309] when choosing slave to read from, should take into account slaveDelay and possibly oplog status Created: 27/Mar/11 Updated: 21/Sep/16 Resolved: 21/Sep/16 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Cluster Management |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Antoine Girbal | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
If a server has a slavedelay, it should probably not be used for reads if possible. |
| Comments |
| Comment by Jeffrey Yemin [ 21/Sep/16 ] |
|
Closing as Won't Fix, though some of the use cases will be satisfied by |
| Comment by Idris Mokhtarzada [ 09/May/12 ] |
|
The oplog part of this looks like it would be resolved by |
| Comment by Antoine Girbal [ 11/Mar/12 ] |
|
as per doc, slaveDelay requires priority=0 and enforces hidden=true As for oplog status, this would be much easier if it got reported by servers in isMaster response. |
| Comment by Jeffrey Yemin [ 10/Mar/12 ] |
|
Don't we already ignore servers with slavedelay? |
| Comment by Idris Mokhtarzada [ 14/Oct/11 ] |
|
What's the status of this issue? Was it ever implemented? In general, if you have a slaveDelay node specified as one of the hosts in your driver, will it try to read data from that node? |