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

Remove rolled back index builds after rollback to a checkpoint

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • Replication
    • ALL
    • Repl 2018-02-26

    Description

      On primaries, we timestamp the beginning of an index build with a timestamp before the "createIndexes" oplog entry. Thus after we roll back to a checkpoint, the index with ready: false may still be around. If we crash and restart, WT will then rebuild the index, even though it doesn't exist on some nodes.

      Attachments

        Issue Links

          depends on

          Task - A task that needs to be done. SERVER-29933 Roll Back to Checkpoint: Notify subsystems that rely on OpObservers to maintain state to rebuild state from data on disk

          • Major - P3 - Major loss of function.
          • Closed
          duplicates

          Task - A task that needs to be done. SERVER-33359 Have RTT storage engines manage rolling back incomplete index builds.

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              william.schultz@mongodb.com William Schultz (Inactive)
              judah.schvimer@mongodb.com Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: