There may be race conditions to handle between getting the index catalog entries and accessing the index build interface. I'm not sure whether it's important to give a snapshot view of indexes via listIndexes, in which case we can cut corners and simplify.
Questions to be addressed in regards to initial sync: if listIndexes returns cursor results, and we are racily adding builderUUIDs, does this affect what we expect to see in the oplog? Like seeing an oplog entry when we don’t expect one? Does the catalog index info have to be acquired at the same timestamp as the config.system.indexBuilds data?
- is depended on by
-
SERVER-39087 move initial sync index creation logic into IndexBuildsCoordinator
-
- Closed
-
-
-
- Closed
-
- related to
-
SERVER-47842 [4.4] listIndexes with includeBuildUUIDs=true in FCV 4.2 reports in-progress index build as completed
-
- Closed
-