The listIndexes command in list_indexes_with_build_uuids.js is run on the secondary after checking the db.currentOp() output. However, this command may read the catalog state before the secondary has completed applying the batch of oplog entries containing the startIndexBuild command. This will lead to the test not detecting the in-progress index build.
- is related to
-
SERVER-51703 index_secondary_wait_for_commit.js - IndexBuildTest.assertIndexes() sees different server state from IndexBuildTest.getIndexBuildOpId()
-
- Closed
-
-
-
- Closed
-