-
Type:
Improvement
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.2.0-rc0
-
Component/s: Replication, Storage
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Epic Link:
-
Sprint:QuInt A (10/12/15)
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 (SERVER-20825). Until then, we will leave the thread enabled by default until then to allow more burn-in time across more workloads.
- is documented by
-
DOCS-9527 Docs for SERVER-20707: Add a new option --enableMajorityReadConcern
-
- Closed
-
- is related to
-
SERVER-22617 SnapshotThread hits invariant due to reading oplog entries out of order
-
- Closed
-
- related to
-
SERVER-20825 Only start snapshot thread when majority read concern is enabled
-
- Closed
-