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

createIndexes command in fsm_workloads/invalidated_cursors.js fails with NoMatchingDocument error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.0-rc7, 4.7.0
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      Execution Team 2020-06-01
    • Linked BF Score:
      22

      Description

      The concurrency test workload invalidated_cursors.js may fail because of an unhandled NoMatchingDocument error in indexbuildentryhelpers ::getIndexBuildEntry()

      Starting in SERVER-48197, the createIndexes command may fail with a NoMatchingDocument error if the index build is aborted after indexbuildentryhelpers acquires the locks on the config.system.indexBuilds collection. For concurrency tests that consider IndexBuildAborted as an acceptable error for createIndexes, we can either:

      • add NoMatchingDocument to the list of acceptable errors; or
      • update the server code to convert NoMatchingDocument errors from getIndexBuildEntry() to IndexBuildAborted.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: