-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
Repl 2019-10-21, Repl 2019-11-04, Repl 2019-11-18
The drivers would benefit from not having to keep their own list of retryable error codes and the server being able to add these whenever it wanted. This would just be codifying the current behavior and (at least at first) shouldn't hit the "exponential error codes" problem that the "Communicate Error Labels to Drivers" project had in design.
- is depended on by
-
DRIVERS-525 Expand use of error labels for RetryableWrites
- Development Complete
- is duplicated by
-
SERVER-43940 Update failCommand fail point to add the RetryableWriteError label to retryable errors
- Closed
- is related to
-
SERVER-43940 Update failCommand fail point to add the RetryableWriteError label to retryable errors
- Closed
-
SERVER-43941 Add "errorLabels" field to failCommand fail point
- Closed
-
SERVER-37324 Investigate potential uses of TransientTransactionError label
- Closed
- related to
-
SERVER-53624 4.4 mongos does not attach RetryableWriteError label to shutdown errors
- Closed
-
SERVER-58195 InterruptedDueToReplStateChange missing 'RetryableWriteError' error label
- Closed
-
SERVER-42951 Test that CRUD operations outside transactions don't throw LockTimeout
- Closed