[SERVER-68571] Update reaper when instantiating collection/index on expired ident Created: 04/Aug/22  Updated: 29/Oct/23  Resolved: 16/Sep/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: Henrik Edin Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-08-22, Execution Team 2022-09-05, Execution Team 2022-09-19, Execution Team 2022-10-03
Participants:

 Description   

A Collection or Index instance can be re-created because the previous one is expired, waiting for cleanup by the reaper. When this occurs we need to update the token held by the reaper to prevent data from being cleaned up under the newly created collection or index instance used for a PIT read before the drop.



 Comments   
Comment by Githook User [ 16/Sep/22 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-68571 Update reaper when instantiating collection/index on expired ident
Branch: master
https://github.com/mongodb/mongo/commit/fc8c8f31dd821369f3fc3d9afb1f7d2cbda0c138

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