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.
- is related to
-
SERVER-56279 Index build failure errors with NoMatchingDocument as cause of commit quorum failing
- Closed
-
SERVER-37726 Make dropIndexes abort in-progress index builds
- Closed
- related to
-
SERVER-48407 createIndexes command in fsm_workloads/drop_index_during_replan.js fails with NoMatchingDocument error
- Closed
-
SERVER-48588 createIndexes command in fsm_workloads/yield_with_drop.js fails with NoMatchingDocument error
- Closed