[COMPASS-6211] Investigate changes in PM-3038: Mongos communicates retryable error labels from shards to drivers Created: 17/Oct/22 Updated: 09/Dec/22 Resolved: 07/Dec/22 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Investigation | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Rhys Howell |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Epic Link: | COMPASS-5985 | ||||||||
| Documentation Changes: | Not Needed | ||||||||
| Sprint: | Iteration Quahog | ||||||||
| Description |
|
Original Downstream Change Summary This is a dependency for DRIVERS-555 to be effective. Description of Linked TicketEpic Summary SummaryExpose RetryableWriteError and NoWritesPerformed error labels from mongos to drivers. MotivationSince MongoDB 4.4 ( The work from DRIVERS-555 (Client Side Operations Timeout) enables applications to set a deadline until which the driver should continue to retry. This may mean an application is willing to retry longer than the duration of the retries performed by mongos. Having mongos propagate back a RetryableWriteError label when it gives up retrying can signal to drivers whether they want to continue retrying themselves. Moreover, drivers also rely on the NoWritesPerformed error label ( Documentation |
| Comments |
| Comment by Rhys Howell [ 07/Dec/22 ] |
|
I don't think we need to do anything here for mongosh. We surface the errors the server/driver returns, so any new label from the server or driver will show up. If we want to do work in improving error reporting we could look at |