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

Leave index builds unfinished when aborted due to rollback or local failure

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Storage Execution

    Description

      When a two-phase index build is torn down and the node is no longer primary, we remove the durable catalog entry using a ghost timestamp. This works, because this ghost write is always rolled back.

      We should leave the index build unfinished it is aborted due to rollback or local failure. By "local failure", I am referring to the case where an index build fails on a secondary, but not from an explicit abortIndexBuild oplog entry.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            louis.williams@mongodb.com Louis Williams
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: