[DRIVERS-1253] Make dropIndexes abort in-progress index builds Created: 18/Feb/20 Updated: 27/May/22 Resolved: 26/May/20 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Server Compat: | 4.3 | ||||||||||||||||||||
| Description |
|
Downstream Change Summary The "dropIndexes" command can now be used to abort in-progress index builds being built in the background. As we can only abort at the builder level granularity, the user must specify all the indexes being built by a single index builder to abort it successfully. This command still retains the previous behaviour of returning "BackgroundOperationInProgressForNamespace" when trying to drop a ready index while there are index builds still in-progress. Description of Linked Ticket dropIndexes should abort in-progress index builds. This should be done after
Lastly, dropIndexes will not write a dropIndexes oplog entry if aborting in-progress builds. Aborting the index will produce an abortIndexBuilds oplog entry, which suffices. This allows rollback via refetch to know that an index was fully built prior to a dropIndexes oplog entry. |
| Comments |
| Comment by Jeremy Mikola [ 18/May/20 ] |
|
During triage, let's determine if this should be closed and consolidated in favor of |
| Comment by Jeremy Mikola [ 08/May/20 ] |
|
I think this should be re-opened for triaging based on later comments in |
| Comment by Esha Bhargava [ 24/Feb/20 ] |
|
No Drivers changes needed. |