[SERVER-44747] Propagate error code from in-progress aborting index build to conflicting index build request Created: 20/Nov/19  Updated: 07/Jan/20  Resolved: 07/Jan/20

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

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Louis Williams
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Sprint: Execution Team 2020-01-13
Participants:

 Description   

When an index build request finds than an identical index build is already in progress, it will normally return with an IndexBuildAlreadyInProgress error. This is retried internally by the createIndexes command.

If the in-progress build has already been aborted, but is slow to tear down, we propagate an IndexBuildAborted error code to the caller. This was done as part of SERVER-43612.

This masks the original cause of aborting the index build. If the index build was aborted by InterruptedDueToReplStateChange, a retryable error, the error code returned to the client is IndexBuildAborted, which is not retryable. This causes tests to break because they cannot retry this operation.


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