[SERVER-47884] Add disableLockFreeReads server parameter Created: 01/May/20  Updated: 29/Oct/23  Resolved: 20/Jul/20

Status: Closed
Project: Core Server
Component/s: Concurrency, Storage
Affects Version/s: None
Fix Version/s: 4.7.0

Type: New Feature Priority: Major - P3
Reporter: Geert Bosch Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-51918 Create feature flag for Lock free reads Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-05-18, Execution Team 2020-06-01, Execution Team 2020-06-15, Execution Team 2020-06-29, Execution Team 2020-07-13, Execution Team 2020-07-27
Participants:

 Description   

A new server parameter --disableLockFreeReads allows turning off the behavior changes described below. On stand-alone nodes and nodes with --enableReadConcernMajority=false this parameter defaults to true.



 Comments   
Comment by Githook User [ 20/Jul/20 ]

Author:

{'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}

Message: SERVER-47884 Add 'disableLockFreeReads' startup server parameter and test suite.

The default for development is currently true, except in the test suite that sets it to false.
Standalone mode and --enableReadConcernMajority=false cause an override to true.
Branch: master
https://github.com/mongodb/mongo/commit/0b915dcc82121fbe11c605fa3f17fd52f796c070

Generated at Thu Feb 08 05:15:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.