-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Fully Compatible
-
v5.0, v4.4
-
Execution Team 2021-02-22, Execution Team 2021-03-08
In an attempt to reproduce some failures, I noticed we have remarkably little coverage of handling spurious WriteConflicts, especially in operations where they are normally unexpected. While most of our code is designed to handle such cases, I think we should exercise these code paths more often, since WiredTiger can return WT_ROLLBACK at any time.
I would suggest enabling the WTWriteConflictException and WTWriteConflictExceptionForReads fail points to a very low frequency (e.g. < 1%) so that most operations can make some progress.
- depends on
-
SERVER-51526 Hybrid index builds can miss writes and crash in the event of a well-timed WriteConflictException
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
SERVER-21332 Add FSM runners that always enable the WTWriteConflictException failpoint
-
- Closed
-