The IndexBuildsCoordinator handles index builds on primary and secondary nodes in the majority of use cases. However, there are a few cases where we also create indexes that do not use the IndexBuildsCoordinator. These cases include:
- Renaming a collection across databases
- Copying indexes from an existing output collection for MapReduce
- Cloning a collection during chunk migration (MigrationDestinationManager)
- related to
-
SERVER-43323 replicated index builds not writing startIndexBuild and commitIndexBuild oplog entries
-
- Closed
-
-
SERVER-43295 Secondaries should start index build on receiving startIndexBuild oplog entry
-
- Closed
-