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

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

      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.)

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

              Created:
              Updated:
              Resolved:
              4 years, 10 weeks, 2 days ago