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

dropIndexes will invariant if it sees complete indexes after successfully aborting a different index build

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.4.0-rc4, 4.7.0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Execution Team 2020-05-18
    • 22

    Description

      An invariant can fail in dropIndexes given the following sequence between command threads A, B, and C:

      Part of the problem here is that index names are not unique to index builds, so while the dropIndexes command can successfully abort an index build, another index by the same name could be created again in a brief window of time before it reacquires its locks.

      In this scenario, we should consider dropping the finished index if we discover that it exists.  This was the previous behavior.

      Attachments

        Activity

          People

            gregory.wlodarek@mongodb.com Gregory Wlodarek
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: