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

Trigger immediate drop of unfinished indexes during startup recovery

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.1.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Execution Team 2022-05-30, Execution Team 2022-06-13

    Description

      During startup recovery after an unclean shutdown (i.e. it can't be resumed), we drop any incomplete-built indexes and rebuild them. When we drop these tables, we queue them for deletion, but we only run the reaper when the minimum of the oldest and checkpoint timestamps are advanced.

      At this point in startup, we have not initialized replication, so we are not advancing the oldest or stable timestamps. We have started the checkpoint thread, but this also only runs every minute.

      This can be problematic after an unclean shutdown due to running out of disk space during an index build. Because the table isn't dropped immediately, we end up with potentially very large files that can't be dropped until the next index build completes.

      Attachments

        Activity

          People

            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: