Details
-
New Feature
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
Fully Compatible
-
Execution Team 2020-02-24, Execution Team 2020-03-09
Description
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.
Attachments
Issue Links
- is documented by
-
DOCS-13462 Investigate changes in SERVER-46123: Make the dropDatabase command abort in-progress index builds
-
- Closed
-
- is duplicated by
-
SERVER-33634 Allow dropDatabase (and dropCollection) to succeed when index build is in progress
-
- Closed
-
- is related to
-
SERVER-43206 All callers of DatabaseImpl::dropCollectionEvenIfSystem must first assert under a lock that no index builds are in progress
-
- Closed
-
-
SERVER-47087 Stepping down the primary when running 'dropDatabase' does not always reset the dropPending flag when the user operation is killed
-
- Closed
-
-
PYTHON-2068 Test Failure - test_session.TestSession.test_unacknowledged_writes
-
- Closed
-
-
SERVER-46649 Test $out with two-phase index builds enabled
-
- Closed
-
- split from
-
SERVER-37963 Update metadata command behaviors to either ignore or interrupt index builds
-
- Closed
-