Propagate error code from in-progress aborting index build to conflicting index build request

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • Execution Team 2020-01-13
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Louis Williams
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: