Currently, index builds are restarted from the beginning. To be able to resume an index build, we require the temporary tables used by the hybrid index build to be preserved on startup and the progress information in the internal index build table (one table per index build).
This ticket implements the resumable index build logic for index builds that were shut down during the side table catch up phase. The internal ident for the index build should have the following phase:
{ _id: <build uuid>,
phase: "drain writes",
...
}
- is depended on by
-
SERVER-50095 Augment ResumableIndexBuildTest to ensure that index builds are resumed from the correct phase
-
- Closed
-
- is related to
-
SERVER-39715 Do not drop index build temp tables on clean shutdown
-
- Closed
-
-
-
- Closed
-
- related to
-
SERVER-50127 Coverity analysis defect 116104: Using invalid iterator
-
- Closed
-
-
-
- Closed
-