[SERVER-20707] Add a new option --enableMajorityReadConcern Created: 30/Sep/15 Updated: 17/May/19 Resolved: 08/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | QuInt A (10/12/15) | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| 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 Githook User [ 08/Oct/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |
| Comment by Githook User [ 08/Oct/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |
| Comment by Mathias Stearn [ 05/Oct/15 ] |
|
Removed 'level' from option name. |
| Comment by Andy Schwerin [ 01/Oct/15 ] |
|
I don't think the word "level" adds any value. I believe that "majority read concern" is sufficiently descriptive. |