[SERVER-46122] Make the drop command abort in-progress index builds Created: 13/Feb/20  Updated: 29/Oct/23  Resolved: 19/Feb/20

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: None
Fix Version/s: 4.3.4

Type: New Feature Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
is documented by DOCS-13430 Investigate changes in SERVER-46122: ... Closed
Duplicate
is duplicated by SERVER-33634 Allow dropDatabase (and dropCollectio... Closed
Issue split
split from SERVER-37963 Update metadata command behaviors to ... Closed
Related
is related to SERVER-43206 All callers of DatabaseImpl::dropColl... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-02-24
Participants:
Linked BF Score: 38

 Description   

While dropping a collection, 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 collection. Secondaries should not abort in-progress index builds but instead wait for the abortIndexBuilds oplog entry.



 Comments   
Comment by Githook User [ 19/Feb/20 ]

Author:

{'username': 'GWlodarek', 'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com'}

Message: SERVER-46122 Make the drop command abort in-progress index builds before dropping the ready indexes and collection itself
Branch: master
https://github.com/mongodb/mongo/commit/95335e138106df460056105e2cf0bec08e45708e

Comment by Githook User [ 19/Feb/20 ]

Author:

{'username': 'GWlodarek', 'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com'}

Message: SERVER-46122 Concurrency tests should expect the 'IndexBuildAborted' error code when dropping collections
Branch: master
https://github.com/mongodb/mongo/commit/37b61a5057dee96f7d0db0b592dd084b459b7824

Generated at Thu Feb 08 05:10:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.