-
Type:
Bug
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
ALL
-
Execution Team 2023-02-20, Execution Team 2023-02-06, Execution Team 2023-03-06
-
0
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In some query stages like delete, we will need to call restoreState() in case the actual delete throws a WCE which invalidates the cursor. But restoreState() can also throw a WCE which is not handled. This can cause the following next() call lands the cursor to the beginning of the collection again, hitting the out-of-order invariant.
- is fixed by
-
SERVER-80859 Reshuffle UpdateStage/DeleteStage's logic to skip restore
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Closed
-
-
SERVER-37861 Add writeConflictRetry to wildcard index multikey metadata path extraction
-
- Closed
-