-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
Fully Compatible
-
Execution Team 2024-10-28, Execution Team 2024-11-11, Storage Execution 2025-06-09
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
We sometimes use write conflict exceptions for events that are actually unrelated to write conflicts (example). Audit these locations and determine whether they warrant a using a different error code and handling policy (e.g. TemporarilyUnavailable).
- is related to
-
SERVER-77542 Internal operations should handle TemporarilyUnavailable and TransactionTooLargeForCache exceptions
-
- Closed
-
-
SERVER-105906 Replace WriteConflictException on lock timeout.
-
- Backlog
-
-
SERVER-105907 Replace Write Conflict Exception on wiredtiger_perpare_conflict::wiredTigerPrepareConflictRetrySlow
-
- Backlog
-
-
SERVER-105908 Replace Write Conflict Exception in WiredTigerRecordStore::getLargestKey
-
- Backlog
-
-
SERVER-105910 Replace Write Conflict Exception in WiredTigerSizeStorer::flush
-
- Backlog
-
- related to
-
SERVER-60839 Introduce a TemporarilyUnavailable error type
-
- Closed
-
-
SERVER-105967 Complete TODO listed in SERVER-63620
-
- Closed
-