When IndexBuildsCoordinator::_registerAndSetUpIndexBuild() is acquiring the collection in order to begin an index build on a standalone or primary node, it may be possible for catalog changes to cause the index build to be initialized on a collection with a different UUID from what is provided to the IndexBuildsCoordinator.
This is applies only when the IndexBuildsCoordinator is enabled for the createIndexes command.
- is depended on by
-
SERVER-39454 Move createIndexes command fully onto the IndexBuildsCoordinator
- Closed
- is related to
-
SERVER-42242 Acquire locks by collection UUID during the createIndexes command
- Closed