[SERVER-68253] Maintain collections and indexes in pending-drop state in the CollectionCatalog Created: 25/Jul/22 Updated: 29/Oct/23 Resolved: 04/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.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 | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Execution Team 2022-08-08 | ||||
| Participants: | |||||
| Linked BF Score: | 135 | ||||
| Description |
|
When instantiating a Collection/IndexCatalog from a durable catalog entry it may contain a collection or index in drop-pending state. We need to be able to recover the instance. The CollectionCatalog should contain a mapping from Ident to weak_ptr of these instances. DDL operations putting collections/indexes in drop-pending should insert into this mapping and the cleanup should happen from the ident reaper when the drop has been performed. |
| Comments |
| Comment by Githook User [ 04/Aug/22 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |