-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Execution Team 2019-12-16
During rollback, we abort any active index builds. The build cleans itself up and removes the durable catalog entry by calling tearDownIndexBuild() here. Because we are not primary, we assign ghost timestamps when cleaning up unfinished indexes.
This is mostly okay, because rollback will always roll-back that write. However it could be possible to take a stable checkpoint between tearing down the build and actually rolling-back. If the server crashed at this point, on startup, the index build won't get rebuilt at all.
It would be more correct to just leave the index build unfinished to avoid ghost timestamping the index build cleanup.
- is duplicated by
-
SERVER-44759 Leave index builds unfinished when aborted due to rollback or local failure
- Closed
- related to
-
SERVER-44190 Adapt hybrid_index_build_on_state_transition.js to work with two phase index builds
- Closed