[SERVER-75259] Data race in WiredTigerRecordStore::getEarliestOplogTimestamp Created: 24/Mar/23  Updated: 29/Oct/23  Resolved: 30/Mar/23

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

Type: Bug Priority: Major - P3
Reporter: Pavithra Vetriselvan Assignee: Jordi Olivares Provencio
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2023-04-03
Participants:
Linked BF Score: 1

 Description   

Due to this call, we can race between truncating the oplog and getting it's earliest timestamp. We could also race between multiple threads calling getEarliestOplogTimestamp at the same time.



 Comments   
Comment by Githook User [ 29/Mar/23 ]

Author:

{'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}

Message: SERVER-75259 Fix race condition during earliest oplog timestamp initialisation
Branch: master
https://github.com/mongodb/mongo/commit/c8c85ca51d1fb0c40c59f135499d5aa3b26f73a5

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