When the primary is building the index with the IndexBuildsCoordinator, there could be two db.currentOp() entries for the index build: one for the command invocation on the client connection and another for the task in the thread pool managed by the IndexBuildsCoordinator. The operation performing the actual work should be the one with a non-empty 'locks' field and should be preferred over the client connection operation.
This affects mostly JS tests that attempt to locate and modify the state of an active index build when the enableIndexBuildsCoordinatorForCreateIndexesCommand server parameter is enabled.
- is depended on by
-
SERVER-39454 Move createIndexes command fully onto the IndexBuildsCoordinator
-
- Closed
-
- is related to
-
SERVER-40917 collstats_shows_ready_and_in_progress_indexes.js should use checkLog instead of currentOp to check for active index builds
-
- Closed
-
-
SERVER-40916 Improve logging of IndexBuildTest::waitForIndexBuildToStart for test failure diagnosis
-
- Closed
-
- related to
-
-
- Closed
-