-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Server
-
Labels:None
----------------------------
Original Description
Documentation and code contradict each other on `--enableMajorityReadConcern`.
Documentation says that in v3.6 majority read concern is always enabled, and that the switch has no effect (https://docs.mongodb.com/v3.6/reference/program/mongod/#cmdoption-mongod-enablemajorityreadconcern)
However, according to https://jira.mongodb.org/browse/SERVER-32022, the switch is re-enabled in v3.6.1.
----------------------------
Description
Scope of changes (files that need work and how much)
Impact to other docs outside of this product
MVP (work and date?)
Resources (e.g. Scope Docs, Invision)
- related to
-
DOCS-12081 Docs for SERVER-36982: Reintroduce enableMajorityReadConcern:false server parameter
- Closed