In SERVER-44186, we added support for allow two phase index builds to continue running on stepdown. The responsibility for completing the index build, which can be observed in the oplog by the presence of the commitIndexBuild oplog entry, will fall on the new primary.
However, since unique index builds have constraints that are set up at the beginning of the build, it was necessary, in SERVER-44397, to temporarily disable failover support, which means unique index builds are aborted on stepdown currently.
In this ticket, we will look into re-enabling failover support for unique indexes.
- is related to
-
SERVER-44397 index build continues to enforce constraints after failing over from primary to secondary
- Closed
-
SERVER-45351 Newly-elected primaries can commit index builds with inconsistencies due to ignoring indexing errors as secondary
- Closed
-
SERVER-44186 allow index builds to continue running on stepdown
- Closed
- related to
-
SERVER-45852 Two-phase index build constraints should be checked at the completion of the index build
- Closed
-
SERVER-45988 add IndexBuildAborted to list of acceptable errors in fsm_workloads/create_index_background_unique.js
- Closed