[SERVER-32208] Remove retrying of OperationFailed in auto_retry_on_network_error.js Created: 07/Dec/17 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Querying, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Jack Mulrow | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | max-triage, neweng, open_todo_in_code | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
There used to be a case where a write command swallowed the original error code and replaced it with OperationFailed, but we believe that has been fixed in Original DescriptionSimilarly to These are the commands I've seen that definitely have this problem, there may be more though: Grepping for "executor error" turns up a few more places where this could be an issue, since it seems like this logic has been copied across a few commands. |
| Comments |
| Comment by Jack Mulrow [ 13/Apr/18 ] |
|
charlie.swanson That sounds good to me. |
| Comment by Charlie Swanson [ 13/Apr/18 ] |
|
jack.mulrow it looks like we actually resolved this under |
| Comment by Jack Mulrow [ 08/Dec/17 ] |
|
charlie.swanson I don't know if there are any existing BFs related to this, I only ran into it locally when I was writing the new retryable_writes_jscore_stepdown_passthrough for |
| Comment by Charlie Swanson [ 08/Dec/17 ] |
|
jack.mulrow can you link us to some instances of these failures so we can know how often this is a problem to help with triaging? I'm aware of |