[DOCS-3963] Comment on: "manual/core/read-preference.txt" Created: 29/Aug/14 Updated: 03/Nov/17 Resolved: 29/Aug/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Prod Location: http://docs.mongodb.org/manual/core/read-preference/ |
||
| Participants: | |
| Days since reply: | 9 years, 24 weeks, 5 days ago |
| Description |
|
In most situations, operations read from secondary members but if no secondary members are available, operations read from the primary. Should this read "operations read from secondary members but if no secondary members are available, operations read from the primary." I am not sure I understand "In most situations" We also aren't seeing this actually work in our code. We have implemented tagging for dataCenters and using secondaryPreffered. We have not seen a drop in queries to the primary. Thanks |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 29/Aug/14 ] |
|
I believe that the documentation is correct here. If you're having an issue with your read preference configuration please consider opening a support case and someone will help figure out what's going on with your deployment. See http://www.mongodb.org/about/support for more information about support cases. |