Loading...

XML

Word

Printable

JSON

Details

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.3.1
Affects Version/s: None
Component/s: Replication
Labels:
- former-quick-wins

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2019-10-21, Repl 2019-11-04, Repl 2019-11-18

Description

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.

Attachments

Issue Links

is depended on by

DRIVERS-525 Expand use of error labels for RetryableWrites

Closed

is documented by

DOCS-13204 Investigate changes in SERVER-41245: Add RetryableWriteError Error Label

Backlog

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

(1 is related to, 3 related to)

Activity

People

Assignee:: Lingzhi Deng

Reporter:: Judah Schvimer

Participants:: Githook User, Jeremy Mikola, Judah Schvimer, Lingzhi Deng, Ratika Gandhi

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Dates

Created:: May 20 2019 05:37:52 PM UTC

Updated:: Oct 29 2023 10:20:50 PM UTC

Resolved:: Nov 06 2019 03:31:27 PM UTC