[SERVER-2373] Dropping an index that is currently being built should kill the building operation Created: 18/Jan/11 Updated: 06/Dec/22 Resolved: 15/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Index Maintenance |
| Affects Version/s: | 1.7.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Lee | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Operating System: | ALL |
| Participants: |
| Description |
|
If a background index is being run, you should be able to dropIndex and drop the index, killing the background index operation if necessary. Right now, the dropIndex is failing because multiple index operations cannot run at the same time. |
| Comments |
| Comment by Eric Milkie [ 15/Nov/16 ] |
|
Interrupting the index build (killOp) will result in the index going away. You can't drop the index because it's not yet committed. |