-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
ALL
-
v8.0, v7.0
-
Execution Team 2024-11-25, Execution Team 2024-12-09
In SkippedRecordTracker::retrySkippedRecords, we don't construct a write unit of work if we only intend to retry key generation without updating the index and tracker. If we do not find the record in the collection, we may attempt to delete the record from the tracker without being in a wuow which could lead to failing this invariant.
This can this happen on step up.
We should also clean up this comment since the feature flag has been removed.
- is related to
-
-
- Backlog
-
-
SERVER-73331 Index builds abort on step-up if key generation errors are found in SkippedRecordTracker
-
- Closed
-
-
SERVER-98417 Add test for records in the skipped record tracker that are no longer found in the collection
-
- Closed
-