[DOCS-9527] Docs for SERVER-20707: Add a new option --enableMajorityReadConcern Created: 05/Dec/16 Updated: 08/Dec/17 Resolved: 08/Dec/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Emily Hall | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | delete-docs-tickets | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 6 years, 9 weeks, 5 days ago | ||||||||
| Epic Link: | PM-134 | ||||||||
| Description |
|
Engineering Ticket Description: Plan: Add a new option --enableMajorityReadConcern. It will be enabled by default on CSRS nodes. When enabled, we will fail to start up if the selected storage engine doesn't support snapshots. When disabled, requests with readMajority=majority will fail with a dedicated error. At some point during the RCs before GA release, we will disable the snapshot thread if --enableMajorityReadConcern is not specified ( |
| Comments |
| Comment by Kay Kim (Inactive) [ 08/Dec/17 ] |
|
bulk closing duplicate tickets created after work was done. |