-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
None
-
Storage Execution
Rollback via recover to a stable timestamp should save indexes from the ident reaper, if the reaper has not already run on that index, meaning dropIndexes occurred far enough in the past that PIT reads can no longer access the index.
I am not sure what kind of timestamping or history cleanup occurs around rollback via refetch, whether indexes can be saved from the reaper.
This must be done after SERVER-38548 introduces two-phase index drop.
- duplicates
-
SERVER-38548 Leverage the KVDropPendingIdentReaper and TimestampMonitor to make index drops two-phase
- Closed
- is related to
-
SERVER-31130 Add javascript test to exercise simple rollback of every supported operation type
- Closed
- related to
-
SERVER-37730 Make the index catalog timestamp aware
- Closed