Loading...

XML

Word

Printable

JSON

Type: New Feature
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.3.4
Affects Version/s: None
Component/s: Index Maintenance
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Execution Team 2020-02-24, Execution Team 2020-03-09
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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.

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

related to

SERVER-86632 plan_cache_drop_database.js should catch DatabaseDropPending errors

Closed

split from

SERVER-37963 Update metadata command behaviors to either ignore or interrupt index builds

Closed

(1 related to, 1 split from)

Assignee:: Gregory Wlodarek
Reporter:: Gregory Wlodarek
Participants:: Githook User, Gregory Wlodarek
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Feb 13 2020 01:18:56 PM UTC
Updated:: Feb 14 2024 05:08:04 PM UTC
Resolved:: Feb 27 2020 03:03:58 AM UTC
Confidence Status Last Update:: 19/Feb/20 2:37 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates