-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
Summary
This exception caused by a lock timeout does not meat the definition of a Write Conflict and should be replaced by a different error code. Consider using a Temporarily Unavailable Exception instead.
- related to
-
SERVER-63620 Evaluate locations that throw WriteConflictExceptions without a real write conflict
-
- Closed
-