[SERVER-46123] Make the dropDatabase command abort in-progress index builds Created: 13/Feb/20  Updated: 29/Oct/23  Resolved: 27/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-13462 Investigate changes in SERVER-46123: ... 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
is related to SERVER-47087 Stepping down the primary when runnin... Closed
is related to PYTHON-2068 Test Failure - test_session.TestSessi... Closed
is related to SERVER-46649 Test $out with two-phase index builds... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-02-24, Execution Team 2020-03-09
Participants:

 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.



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

Author:

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

Message: SERVER-46123 Make the dropDatabase command abort in-progress index builds
Branch: master
https://github.com/mongodb/mongo/commit/86cdfdd6e58a9853b39c6f4dc7f14e7210bd7c9f

Comment by Githook User [ 26/Feb/20 ]

Author:

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

Message: SERVER-46123 Skip out_drop_temp_collection.js for two-phase index builds, concurrency tests should expect the DatabaseDropPending error
Branch: master
https://github.com/mongodb/mongo/commit/463256caf5ae03d1efa9db7d9405b5d78c89c068

Comment by Githook User [ 26/Feb/20 ]

Author:

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

Message: SERVER-46123 Check whether the database is drop pending for aggregation operations
Branch: master
https://github.com/mongodb/mongo/commit/e423a7ce2f5e514054dbbdb4af838e64c8edd11a

Comment by Githook User [ 26/Feb/20 ]

Author:

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

Message: SERVER-46123 Remove ScopedStopNewDatabaseIndexBuilds/ScopedStopNewCollectionIndexBuilds and add the ability to abort index builds on the database without having to wait
Branch: master
https://github.com/mongodb/mongo/commit/86e9d861dd056cdd71ff191ad032cc392bf9071a

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