[SERVER-82346] ChangeCollectionTruncateMarkers read _lastHighestRecordId without mutex Created: 20/Oct/23  Updated: 29/Oct/23  Resolved: 23/Oct/23

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

Type: Bug Priority: Major - P3
Reporter: Yujin Kang Park Assignee: Yujin Kang Park
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-81485 More robust test coverage for change ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution EMEA Team 2023-10-30
Participants:

 Description   

In ChangeCollectionTruncateMarkers::_hasExcessMarkers we useĀ 
getPartialMarker to read _lastHighestRecordId. Accesses to this variable should be protected with _lastHighestRecordMutex, but getPartialMarker allows doing the read without locking.



 Comments   
Comment by Githook User [ 23/Oct/23 ]

Author:

{'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}

Message: SERVER-82346 Fix truncate marker _lastHighestRecordId read not taking mutex
Branch: master
https://github.com/mongodb/mongo/commit/864667cbe0a9811a85fff47d1fcb657f3ee91dfd

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