[DOCS-12081] Docs for SERVER-36982: Reintroduce enableMajorityReadConcern:false server parameter Created: 27/Sep/18  Updated: 13/Nov/23  Resolved: 08/Oct/18

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.0.3, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

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

Issue Links:
Documented
documents SERVER-36982 Reintroduce enableMajorityReadConcern... Closed
Related
related to DOCS-12104 Docs for SERVER-37227: Reintroduce en... Closed
is related to DOCS-11977 Update --enableMajorityReadConcern se... Closed
Participants:
Days since reply: 5 years, 19 weeks, 6 days ago
Epic Link: DOCSP-1769

 Description   

Description

Description:

After this ticket, the enableMajorityReadConcern:false server parameter will be available in 4.0. This parameter should be recommended for replica sets containing arbiters. Single replica set transactions are supported with enableMajorityReadConcern:false, but change streams are not yet supported.

Engineering Ticket Description:

The enableMajorityReadConcern:false option exists on 3.6, to allow the server to avoid holding on to all history since the majority commit point. We would like to add this option on 4.0 to address pain due to commit point lag in replica sets with arbiters.

This work should include adding the enableMajorityReadConcern:false Evergreen variant to 4.0, which was introduced inĀ SERVER-36083. This variant should include all of transactions tests on 4.0.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)


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