[DOCS-9367] summarize use of writeConcernMajorityJournalDefault Created: 22/Nov/16 Updated: 23/Nov/16 Resolved: 23/Nov/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0 |
| Type: | Improvement | Priority: | Critical - P2 |
| Reporter: | Eric Milkie | 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: | 7 years, 12 weeks ago | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
If any voting node in the set does not journal (inMemory or journaling disabled), you must set writeConcernMajorityJournalDefault to false. When set to false, replication waits will no longer wait for writes to be durable. This includes w:majority writes, the user/group admin commands, the replSetStepDown command, and possibly others I'm not thinking of. With this flag set to false, majority acknowledged writes could possibly roll back, in the face of one node failure. |
| Comments |
| Comment by Githook User [ 23/Nov/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 23/Nov/16 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |