[SERVER-37843] Create an index reaper for two-phase index drop Created: 31/Oct/18  Updated: 29/Oct/23  Resolved: 30/Nov/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.6

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done before SERVER-37730 Make the index catalog timestamp aware Closed
Related
related to SERVER-38449 TemporaryKVRecordStore should fail wi... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-12-03
Participants:

 Description   

Create a reaper to schedule the second phase of drop index for when the index's 'death' timestamp becomes checkpointed.

The catalog should have 1st and 2nd phase index drop functions. The 1st phase should call into the reaper with information to identify the index and a timestamp at which to start the 2nd phase. The reaper should call into the catalog to execute the second phase on the index information.

The reaper will use the functionality built in SERVER-38128 to be alerted when the 'death' timestamp becomes checkpointed.



 Comments   
Comment by Githook User [ 30/Nov/18 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-37843 add KVDropPendingIdentReaper
Branch: master
https://github.com/mongodb/mongo/commit/401151f1d29e7d88f4abf10c7ca92739dbc55336

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