-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
Execution Team 2023-03-06, Execution Team 2023-03-20
After SERVER-73330, index builds abort immediately when a key generation error is encountered, instead of waiting until commit time. Secondaries will still record those errors in the SkippedRecordTracker. To make this expectation true across replication state transitions, during step-up the new primary should check if any skipped records still result in a key generation error, and abort the index build if so.
- depends on
-
SERVER-73330 Index builds immediately abort on non-duplicate key generation error
- Closed
- related to
-
SERVER-97462 Retrying skipped records can try deleting record without wuow
- In Progress
-
SERVER-97300 IndexBuildsCoordinator-StepUp incorrectly assumes that it will always be run as primary or be killed by step down
- Closed