[SERVER-36982] Reintroduce enableMajorityReadConcern:false server parameter Created: 04/Sep/18  Updated: 29/Oct/23  Resolved: 24/Sep/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.0.3

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

Issue Links:
Depends
is depended on by SERVER-36985 Test single replica set transactions ... Closed
Documented
is documented by DOCS-12081 Docs for SERVER-36982: Reintroduce en... Closed
Problem/Incident
Related
is related to SERVER-32022 allow enableMajorityReadConcern=false... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-09-10, Repl 2018-09-24, Repl 2018-10-08
Participants:
Linked BF Score: 0

 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.



 Comments   
Comment by Githook User [ 25/Sep/18 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-36982 Fix Jepsen mmap and Linux (no journal) failures
Branch: v4.0
https://github.com/mongodb/mongo/commit/7ea530946fa7880364d88c8d8b6026bbc9ffa48c

Comment by Githook User [ 24/Sep/18 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-36982 Reintroduce enableMajorityReadConcern:false server parameter
Branch: v4.0
https://github.com/mongodb/mongo/commit/7cb5d08b50cfd024a0c587d897a969d81a084dde

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