Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-37733

Optimize rollback via refetch of dropIndexes using the index catalog versioning

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 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.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: