[SERVER-45988] add IndexBuildAborted to list of acceptable errors in fsm_workloads/create_index_background_unique.js Created: 05/Feb/20  Updated: 19/Feb/20  Resolved: 19/Feb/20

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

Type: Improvement Priority: Minor - P4
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-37726 Make dropIndexes abort in-progress in... Closed
is related to SERVER-44654 allow unique index builds to continue... Closed
Sprint: Execution Team 2020-02-24
Participants:
Linked BF Score: 8

 Description   

Starting In SERVER-43612, the create_background_index_unique.js concurrency test workload may get a IndexBuildAborted error from the createIndexes command if there is an existing index build currently being torn down. Previously, we would have gotten a IndexBuildAlreadyInProgress error. This ticket proposes to make IndexBuildAborted an acceptable error for this test workload (similar to what's being done for IndexBuildAlreadyInProgress)



 Comments   
Comment by Benety Goh [ 19/Feb/20 ]

The work described in this ticket was completed as part of SERVER-37726 in this commit.

Comment by Benety Goh [ 05/Feb/20 ]

This ticket could also be considered a temporary workaround until SERVER-44654 is fixed.

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