-
Type:
New Feature
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Concurrency, Testing Infrastructure
-
None
-
Fully Compatible
-
STM 2019-03-25
An insert or update operation retries ad infinitum on a unique key violation that results from the effects of an active transaction (read: a transaction not yet committed or aborted). This behavior is demonstrated by the write_conflicts_with_non_txns.js test. In order to allow the rollback fuzzer to generate randomized insert and update operations that may trigger unique key violations without hanging, it would be useful to add a failpoint to the writeConflictRetry() function where it doesn't do any retry logic and instead has the command fail with a WriteConflict error response.
- related to
-
SERVER-79123 Tests enabling skipWriteConflictRetries failpoint incompatible with index build abort
-
- Closed
-
-
SERVER-40103 Improve retry behavior of non-txn writes conflicting with txns
-
- Closed
-
-
-
- Closed
-