[SERVER-70550] Unsynchronized access to _oplog in LocalOplogInfo Created: 13/Oct/22  Updated: 05/Jan/23  Resolved: 05/Jan/23

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

Type: Bug Priority: Major - P3
Reporter: Yuhong Zhang Assignee: Fausto Leyva (Inactive)
Resolution: Duplicate Votes: 0
Labels: tsan
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-70551 Fix data race between acquireOplogCol... Closed
Operating System: ALL
Sprint: Execution Team 2022-12-12, Execution Team 2022-11-28, Execution Team 2022-12-26, Execution Team 2023-01-09
Participants:
Linked BF Score: 11

 Description   

When modifying and accessing the member _oplog in LocalOplogInfo, a data race can happen, for example, between the OplogCapMaintainerThread and the LocalOplogInfo



 Comments   
Comment by Fausto Leyva (Inactive) [ 05/Jan/23 ]

Upon further investigation, this ticket duplicates SERVER-69419 which is a duplicate of SERVER-70551 and has now been fixed. 

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