[SERVER-37733] Optimize rollback via refetch of dropIndexes using the index catalog versioning Created: 24/Oct/18 Updated: 06/Dec/22 Resolved: 16/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
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 |
| Comments |
| Comment by Benety Goh [ 16/Jul/19 ] |
|
The work is done in |