[DRIVERS-2128] Retryable writes spec should mention why write concern timeout errors are not retried Created: 15/May/18 Updated: 24/Feb/23 Resolved: 24/Feb/23 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | Retryability |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Trivial - P5 |
| Reporter: | Shane Harvey | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Driver Changes: | Needed | ||||
| Description |
|
A write concern timeout error indicates that the command succeeded but failed to meet the specified writeConcern within the given time limit. Attempting to retry would implicitly double the application’s wtimeout value so drivers do not retry. The same is true for timeout errors due to maxTimeMS. |