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

Recoverable Rollback: Extend dropIndexes oplog entry to include dropped index spec

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.5.5
    • Replication
    • None
    • Fully Compatible
    • Repl 2017-03-06, Repl 2017-03-27
    • 0

    Description

      Currently, rolling back a dropIndexes operation in the oplog requires a full resync of the collection documents and metadata.

      This ticket proposes to extend the oplog entry for deleteIndexes to include the specification of the index that is being dropped so that we can recreate the index on rollback without any communication with the sync source.

      Additionally, if there are multiple indexes dropped, a separate oplog entry should be generated for each dropped index.

      Attachments

        Issue Links

          Activity

            People

              judah.schvimer@mongodb.com Judah Schvimer
              benety.goh@mongodb.com Benety Goh
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: