SERVER-41968 IndexBuildTest.getIndexBuildOpId() not selective enough when IndexBuildsCoordinator is enabled

• 
• Closed

SERVER-42015 hybrid_index_with_updates.js hangs when IndexBuildsCoordinator is enabled

• 
• Closed

SERVER-42154 change_streams_primary_shard_unaware.js fails when IndexBuildsCoordinator is enabled

• 
• Closed

SERVER-42272 IndexBuildsCoordinator crashes on index build with duplicate index names

• 
• Closed

SERVER-42280 IndexBuildsCoordinator starts index build on wrong collection

• 
• Closed

SERVER-42281 IndexBuildsCoordinator fails to clean up index build when lock acquisition times out

• 
• Closed

SERVER-42353 indexbg_shutdown.js interrupts index build on secondary prematurely

• 
• Closed

SERVER-42383 IndexBuildsCoordinator may deadlock while cleaning up multiple index builds on the same collection

• 
• Closed

SERVER-39224 Explore why queryoptimizer3.js fails using the IndexBuildsCoordinator, then fix it

• 
• Closed

SERVER-39225 Update kill_rooted_or.js / IndexBuildsCoordinator to gracefully handle index build already in-progress errors

• 
• Closed

SERVER-39585 Explore whether index build failpoint 'crashAfterStartingIndexBuild' requires dropping locks to wait for durability

• 
• Closed

SERVER-39589 Handle collection being dropped between createIndexes command implicit collection creation and IndexBuildsCoordinator setting up the index build

• 
• Closed

SERVER-41844 add evergreen builder for createIndexes IndexBuildsCoordinator mode

• 
• Closed

SERVER-41978 add no_passthrough task to IndexBuildsCoordinator evergreen builder

• 
• Closed

SERVER-41896 Take a unique_ptr as an argument to RecoveryUnit::registerChange()

• 
• Closed