[DOCS-10942] Docs for SERVER-31350: make enableMajorityReadConcern parameter a no-op Created: 25/Oct/17  Updated: 29/Oct/23  Resolved: 26/Oct/17

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 3.6.0-rc1

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

Issue Links:
Documented
documents SERVER-31350 make enableMajorityReadConcern parame... Closed
Participants:
Days since reply: 6 years, 15 weeks, 6 days ago
Epic Link: DOCS: 3.6 Server

 Description   

Documentation Request Summary:

Need to remove mentions of --enableMajorityReadConcern. In the release notes, mention that the parameter is deprecated and now has no effect, as MajorityReadConcern is now always enabled in 3.6.

Engineering Ticket 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 [ 26/Oct/17 ]

Author:

{'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}

Message: DOCS-10942 obsolete enableMajorityReadConcern
Branch: master
https://github.com/mongodb/docs/commit/e44909e21a97bff63a2e1ae1a241598bf2c0be1f

Generated at Thu Feb 08 08:01:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.