[SERVER-31350] make enableMajorityReadConcern parameter a no-op Created: 02/Oct/17  Updated: 30/Oct/23  Resolved: 21/Oct/17

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.6.0-rc1

Type: Task Priority: Major - P3
Reporter: Eric Milkie Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-10942 Docs for SERVER-31350: make enableMaj... Closed
Related
is related to SERVER-32022 allow enableMajorityReadConcern=false... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage 2017-10-23, Storage 2017-11-13
Participants:

 Description   

--enableMajorityReadConcern should now have no effect (but not return an error). We can also eliminate the error that results from using this parameter on a storage engine that doesn't support snapshots.
Additionally, we can remove isMajorityReadConcernEnabled() from ReplSettings.



 Comments   
Comment by Githook User [ 21/Oct/17 ]

Author:

{'email': 'daniel.gottlieb@mongodb.com', 'name': 'Daniel Gottlieb', 'username': 'dgottlieb'}

Message: SERVER-31350: Make enableMajorityReadConcern a noop
Branch: master
https://github.com/mongodb/mongo/commit/367d31e1da549c460ae710a8cc280f4c235ab24f

Generated at Thu Feb 08 04:26:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.