[SERVER-47653] dropIndexes() method can find completed indexes indexes despite aborting index builds. Created: 20/Apr/20 Updated: 06/Dec/22 Resolved: 20/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
In dropIndexes() method, between line 344 & line 350, new index builds can get started and committed after the dropIndexes cmd was able to abort the index builds successfully. This means, noneReady over here can be false as it can find ready indexes in the index catalog, resulting in this invariant failure. |
| Comments |
| Comment by Louis Williams [ 20/Apr/20 ] |
|
I believe this duplicates |