[SERVER-83195] Fix data race on maxOplogSize Created: 13/Nov/23  Updated: 14/Nov/23  Resolved: 14/Nov/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc0

Type: Bug Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Dan Larkin-York
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2023-11-27
Participants:
Linked BF Score: 127

 Description   

Currently the WiredTigerRecordStore has an optional integer member for the maximum oplog size. This member is subject to data races, which can be solved by guaranteeing atomic access.



 Comments   
Comment by Githook User [ 14/Nov/23 ]

Author:

{'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}

Message: SERVER-83195 Fix data race on maxOplogSize
Branch: master
https://github.com/mongodb/mongo/commit/723e5bf62df881258b2dfe317461a0d1c0f134f5

Generated at Thu Feb 08 06:51:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.