[DOCS-7136] Include usage suggestions for ReadConcern.Majority Created: 11/Feb/16 Updated: 11/Jan/17 Resolved: 16/Feb/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Critical - P2 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 8 years, 1 day ago | ||||||||
| Description |
|
Specifically talk about WriteConcern.Majority and how the "majority" point in replication is at the point of the write, not read. Make it clear that you really want to use both together and reading from the primary. This is important when expanding a replica set where the majority number grows, like a reconfig going from 1->5 nodes for example. |
| Comments |
| Comment by Githook User [ 16/Feb/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |