Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-48160

remove IndexBuildsCoordinator::_tryAbort() fatal assertion 4656001 for missing index build thread

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.0-rc10, 4.7.0
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.4
    • Sprint:
      Execution Team 2020-05-18
    • Linked BF Score:
      18

      Description

      Consider removing the fatal assertion for 4656001; or convert to a non-fatal user assertion.

      In IndexBuildsCoordinator::_tryAbort(), it is a fatal error if we are unable to look up the OperationContext of an index build to interrupt using the ReplIndexBuildState::opId (set at index build startup). This fatal assertion was originally introduced in SERVER-46560. Until SERVER-47605, we would occasionally hit this fatal assertion during testing.

      This assertion does not really suggest a crash-worthy scenario because if the OperationContext for an index build cannot be found, it would mean that the index build has completed (committed or aborted) and there would not be any OperationContext to interrupt for the user-initiated abort request.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              benety.goh Benety Goh
              Reporter:
              benety.goh Benety Goh
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: