[DRIVERS-525] Expand use of error labels for RetryableWrites Created: 11/Jul/18 Updated: 28/Oct/23 Resolved: 14/Oct/20 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Critical - P2 |
| Reporter: | Rathi Gnanasekaran | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Server Compat: | 4.3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Quarter: | FY20Q4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Start date: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| End date: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Calendar Time: | 0 minutes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Useful Info SummaryA write error is now considered retryable if it has a RetryableWriteError label in the "errorLabels" field. See the Determining Retryable Writes section for more information on how the driver should determine which write errors are retryable. This change also involves implementing new spec tests that use the failCommand fail point to make sure that drivers are retrying writes based on the presence of the RetryableWriteError label, rather than error codes. See this PR for complete changes. |
| Comments |
| Comment by Alexander Golin (Inactive) [ 14/Oct/20 ] |
|
Closing out as the only remaining dependent ticket is a Server bug which has been identified as "works as designed" in the comment thread here |
| Comment by Jeremy Mikola [ 14/Sep/20 ] |
|
SPEC-1420 was originally linked with |