The server explicitly disallows enableMajorityReadConcern:false to be specified on the command line when starting mongod. Any team that current sets this server parameter to false will be affected.
Since we are removing support for the behaviors gated by that server parameter, teams should also be able to remove testing and code using eMRC=false. Please see PM-1769 for more information about what else the server is planning to remove.
Description of Linked Ticket
WiredTiger recently completed an investigation of the feasibility of removing enableMajorityReadConcern:false now that WT has durable history. After reviewing the findings of that investigation, we are moving forward with Removing Support for enableMajorityReadConcern:false. Durable History addresses cache pressure concerns around majority commit point lag allowing for the removal of eMRC:false (a mode of operation that does not allow distributed transactions and other features).
We need to disable support for eMRC:false as a first step.
In a future release, we will fully remove support for eMRC:false.
Scope of changes
Review https://docs.mongodb.com/manual/reference/read-concern-majority/#disable-read-concern-majority and possibly other mentions?
One approach might be to replace that section with a blurb like 'Starting in MDB 5.0, you can't do this. If you're an older version, refer to those docs to see how to disable maj RC."
Impact to Other Docs
Does this also apply to the replication / sharding settings / parameters?
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)