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

Leverage the KVDropPendingIdentReaper and TimestampMonitor to make index drops two-phase

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.7
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Storage NYC 2018-12-31, Storage NYC 2019-01-14

      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.

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: