[SERVER-38548] Leverage the KVDropPendingIdentReaper and TimestampMonitor to make index drops two-phase Created: 11/Dec/18 Updated: 29/Oct/23 Resolved: 01/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| 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: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | Storage NYC 2018-12-31, Storage NYC 2019-01-14 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
Probably need to remove the special rollback logic for recreating the index when a drop is rolled back. Recover to a stable timestamp reverts the __mdb_catalog back to a time when the index catalog entry was present, but a WT table drop cannot be rolled back, so the index is specially recreated during rollback. We will need special logic either to remove pending drop idents from the ident reaper or reset the ident reaper during rollback. |
| Comments |
| Comment by Githook User [ 01/Jan/19 ] |
|
Author: {'username': 'benety', 'email': 'benety@mongodb.com', 'name': 'Benety Goh'}Message: If drop-pending idents are supported by the storage engine, catalog::openCatalog() will not need |
| Comment by Githook User [ 31/Dec/18 ] |
|
Author: {'username': 'benety', 'email': 'benety@mongodb.com', 'name': 'Benety Goh'}Message: constructor accepts KVStorageEngineInterface instead of KVEngine |
| Comment by Githook User [ 31/Dec/18 ] |
|
Author: {'username': 'benety', 'email': 'benety@mongodb.com', 'name': 'Benety Goh'}Message: |
| Comment by Githook User [ 31/Dec/18 ] |
|
Author: {'username': 'benety', 'email': 'benety@mongodb.com', 'name': 'Benety Goh'}Message: |