[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:
Depends
Duplicate
duplicates SERVER-47319 dropIndexes will invariant if it sees... Closed
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 SERVER-47319. Reopen if that's not correct.

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