-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2026-11-09
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The test rename_collection_with_in_progress_index_builds.js starts the rename too early. Its readiness check returns before the server has recorded the index, so the rename never fails fast as the test expects. The rename and the index build then wait for each other until Evergreen stops the task.
hangIndexBuildOnShard0() uses IndexBuildTest.waitForIndexBuildToStart() to decide the index build has started. That helper polls $currentOp for a createIndexes operation, which shard0 reports before the index is added to the catalog in _setUpIndexBuild(). If the test starts the rename in that window, the rename coordinator's listIndexes check for in-progress index builds misses the build, so the rename continues instead of failing with BackgroundOperationInProgressForNamespace.