[SERVER-70551] Fix data race between acquireOplogCollectionForLogging and initializeStorageControlsForReplication Created: 13/Oct/22  Updated: 29/Oct/23  Resolved: 20/Oct/22

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

Type: Task Priority: Major - P3
Reporter: Frederic Vitzikam Assignee: Frederic Vitzikam
Resolution: Fixed Votes: 0
Labels: tsan
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-69419 Race condition in setting/accessing L... Closed
is duplicated by SERVER-70550 Unsynchronized access to _oplog in Lo... Closed
Related
Backwards Compatibility: Fully Compatible
Participants:
Linked BF Score: 35

 Description   

TSAN found a data race in https://jira.mongodb.org/browse/BF-26306

It can be addressed by initializing the oplog collection pointer before the thread reading it is spawned instead of just after.



 Comments   
Comment by Githook User [ 18/Oct/22 ]

Author:

{'name': 'Frederic Vitzikam', 'email': 'frederic.vitzikam@mongodb.com', 'username': 'fredvitz'}

Message: SERVER-70551 Remove a data race on the oplog collection cached pointer in ReplicationCoordinatorImpl::startup
Branch: master
https://github.com/mongodb/mongo/commit/5339401de304755e29917ca5f5dffe07c9654c6c

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