[SERVER-82031] Audit change collection truncate markers use of abandonSnapshot() Created: 10/Oct/23  Updated: 29/Oct/23  Resolved: 18/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: Haley Connelly 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
related to SERVER-81980 Make PreImagesTruncateManager avoid c... In Code Review
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution EMEA Team 2023-10-16, Execution EMEA Team 2023-10-30
Participants:

 Description   

ChangeStreamChangeCollectionManager::removerExpiredChangeCollectionDocumentsWithTruncate() holds a collection pointer, but abandons the snapshot before issuing a range truncate. 

A collection instance is only valid while a reference to the catalog instance is held or stashed and as long as the storage snapshot remains open. 

All of the change collection truncate marker code should be audited for improper use of abandonSnapshot()



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

Author:

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

Message: SERVER-82031 Remove use of abandonSnapshot in change collection truncate
Branch: master
https://github.com/mongodb/mongo/commit/f78e1d1c0c8cdaed5fcb1673da8512bc7438bb2f

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