[SERVER-69295] Mongos NoWritesPerformed errors MUST return original error Created: 31/Aug/22 Updated: 17/Nov/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Preston Vasquez | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
The existing behavior of mongos is to not propagate errors with the RetryableWriteError label, and instead retry internally. In this case, because the drivers cannot reliably maintain error handling logic for errors labeled with NoWritesPerfomed (that is drivers have no access to the original error), the internal behavior of mongos should be modified to meet the following condition:
|