[DOCS-2885] Nonsensical note in read prefs page Created: 10/Mar/14 Updated: 16/Mar/15 Resolved: 25/Mar/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | audit-2014 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 47 weeks, 2 days ago | ||||
| Description |
|
This page: http://docs.mongodb.org/manual/core/read-preference/ Says: "In general, do not use primary and primaryPreferred to provide extra capacity." That doesn't make much sense. Did you mean "secondary and secondaryPreferred"? Additionally, there's no explanation of why the reader shouldn't do whatever it is the note is warning against. The latter problem may be solved in the course of Anyway it's redundant with the later graf, "If read operations account for a large percentage of your application’s traffic, distributing reads to secondary members can improve read throughput." I'd just delete this note. |
| Comments |
| Comment by Githook User [ 25/Mar/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 25/Mar/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |