[SERVER-85284] Two or more indexes being created cannot be terminated normally Created: 17/Jan/24 Updated: 30/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 7.0.6, 5.0.25, 4.4.29, 6.0.14 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | FirstName lipengchong | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | Bug, storex-ranked | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: | createIndex with a big table in different createIndex
then dropIndexes
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: |
| Description |
|
After 4.4 version, index creation is done in the background, and is Simultaneous Indexing. We can execute dropIndexes to terminate the index being created.
|
| Comments |
| Comment by Chris Kelly [ 20/Jan/24 ] | ||||||||||||||||||||||||||||||
|
Hi! Thanks for your report! Starting in MongoDB 5.2, you should be able to use dropIndexes to drop existing indexes on the same collection even if there is a build in progress on another index. In earlier versions, attempting to drop a different index during an in-progress index build results in a BackgroundOperationInProgressForNamespace error. When I try creating these two indexes on a large collection, and attempt to drop them using {{ {dropIndexes:"yourCollection",index:["field1_1","field2_1"]}}} :
I am assigning this to the relevant team to take a further look. |