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.
- is duplicated by
-
SERVER-37733 Optimize rollback via refetch of dropIndexes using the index catalog versioning
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Closed
-