[SERVER-39224] Explore why queryoptimizer3.js fails using the IndexBuildsCoordinator, then fix it Created: 28/Jan/19  Updated: 27/Oct/23  Resolved: 22/Feb/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-39454 Move createIndexes command fully onto... Closed
Related
is related to SERVER-32567 Replace queryoptimizer3.js with FSM test Closed
Sprint: Storage NYC 2019-02-11, Storage NYC 2019-02-25
Participants:
Linked BF Score: 45
Story Points: 5

 Description   

"So that test has one thread repeatedly recreate a collection with indexes, bulk insert a bunch of docs and do a single index table scan. And a second thread drop the collection repeatedly, to check that index table scan cursors get aborted on dropCollection."



 Comments   
Comment by Dianna Hohensee (Inactive) [ 22/Feb/19 ]

SERVER-39589 made a change to the IndexBuildsCoordinator to return NamespaceNotFound errors, and SERVER-39329 (here) turned those into OK command responses, so the test no longer gets an error when createIndexes races with dropCollection.

Comment by Dianna Hohensee (Inactive) [ 14/Feb/19 ]

queryoptimizer3.js fails because we no longer implicitly create the collection if it does not exist and create the index under a continuous lock.

Generated at Thu Feb 08 04:51:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.