[DRIVERS-2066] Investigate whether newer server versions return "not master" or "node is recovering" error messages Created: 22/Oct/19 Updated: 31/Mar/22 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | Retryability |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Minor - P4 |
| Reporter: | Emily Giurleo (Inactive) | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Driver Changes: | Needed | ||||||||
| Description |
|
In the Retryable Writes spec, it is stated that an error is retryable if it is "a server error response without an error code or one different from those listed above, but with an error message containing the substring 'not master' or 'node is recovering'". It is unclear whether newer versions of the server still return error messages like these without the appropriate error codes. If not, this can be clarified in the Retryable Writes spec. If so, perhaps these errors can be assigned the proper error codes/error labels. Either way, the drivers can stop parsing error message strings as older versions of MongoDB are deprecated. |
| Comments |
| Comment by Emily Giurleo (Inactive) [ 24/Oct/19 ] |
|
siyuan.zhou Yes, 100% agreed. |
| Comment by Siyuan Zhou [ 24/Oct/19 ] |
|
Alternatively, we could update the use of error codes or give them new error codes. Backward compatibility might be an issue. The idea is to codify the contract of write concern errors between server and driver. |