Details
-
Type:
Task
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.7.0
-
Component/s: None
-
Labels:None
-
Last comment by Customer:true
-
Story Points:3
-
Epic Link:
Description
Description
Storage engines that do not support majority read concern but are started with the --enableMajorityReadConcern option will fail to startup with an error message.
See this test for the error message: https://github.com/mongodb/mongo/blob/56b83070a83b2bf134a54063b27c2b48b22dd852/jstests/noPassthrough/supports_read_concern_majority.js
Description of Linked Ticket
The enableMajorityReadConcern server parameter defaults to true, even when using a storage engine where supportsReadConcernMajority() is false. Ideally it should default to false in such cases, however, implementing this is probably more effort than it's worth (it only affects test storage engines). Instead, storage engine creation/init should check if supportsReadConcernMajority is false and enableMajorityReadConcern is true, and handle it accordingly: either force enableMajorityReadConcern to false (if it isn't too late to do that), or else abort startup with an error message (saying that this combination isn't valid and enableMajorityReadConcern must be disabled to run with this storage engine).
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- documents
-
SERVER-49392 Make storage engine init check that enableMajorityReadConcern is compatible with supportsReadConcernMajority
-
- Closed
-