Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13462

Investigate changes in SERVER-46123: Make the dropDatabase command abort in-progress index builds

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.3.4
    • manual

    Description

      Description

      Downstream Change Summary

      The "dropDatabase" command now aborts in-progress index builds on all the collections belonging to the specified database being dropped. After any in-progress index builds are aborted, we proceed with dropping each collection, ready indexes for each collection and the database itself. Previously, if there were any in-progress index builds on any collection belonging to the database, the command would return the "BackgroundOperationInProgressForNamespace" error code.

      Description of Linked Ticket

      While dropping a database, it should abort any in-progress index builds.

      Aborting the index will produce an abortIndexBuilds oplog entry, which suffices for in-progress index builds when dropping the database. Secondaries should not abort in-progress index builds but instead wait for the abortIndexBuilds oplog entry.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

      Attachments

        Issue Links

          Activity

            People

              jeffrey.allen@mongodb.com Jeffrey Allen
              backlog-server-pm Backlog - Core Eng Program Management Team
              Githook User Githook User
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                2 years, 27 weeks, 5 days ago