-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution NAMER
-
Fully Compatible
-
ALL
-
Execution NAMR Team 2023-09-04
-
0
Index builds handle WriteConflicts while aborting, and it is not expected that the operation fails as it means the index build ended up partially teared down, triggering this fassert.
The initial sync fuzzer, and potentially other tests, enable the skipWriteConflictRetries and can trigger the fassert.
- is related to
-
SERVER-49396 Only activate skipWriteConflictRetries failpoint for user connections
- Closed
-
SERVER-40062 Add failpoint to skip doing retries on WriteConflictExceptions
- Closed
-
SERVER-73292 Add internal voteAbortIndexBuild command
- Closed
-
SERVER-40103 Improve retry behavior of non-txn writes conflicting with txns
- Closed
-
SERVER-40105 Improve diagnostic information in currentOp for excessive write conflicts and prepare conflicts
- Closed