SERVER-39335 allowed callers of IndexBuildsCoordinator::startIndexBuild() to bypass the thread pool and invoke the index building functions directly. This was necessary to support synchronous index builds during replica set transitions that used DBDirectClient.createIndexes(). Removing this bypass functionality will improve our ability to reason about the environment and context of index builds managed by the IndexBuildsCoordinator.
Currently, the two known callers that call into the IndexBuildsCoordinator synchronously are generateSystemIndexesForExistingCollection() and ShardingCatalogManager::initializeConfigDatabaseIfNeeded().
- is depended on by
-
SERVER-43692 enable two phase index builds by default
-
- Closed
-
- is related to
-
SERVER-39335 IndexBuildsCoordinator::_runIndexBuild() hangs while transitioning from SECONDARY to PRIMARY
-
- Closed
-
-
SERVER-43697 Create helper functions for building indexes with the IndexBuildsCoordinator
-
- Closed
-