[SERVER-43042] Add option to control (or disable) the number of query retries in mongos Created: 26/Aug/19 Updated: 06/Dec/22 Resolved: 30/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Mark Brinsmead | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
Mongos routers will, under certain circumstances, restart interrupted queries when an election occurs in a shard. When the election was triggered by an event (such as OOM) caused by workload, the workload causing the failure may be restarted, causing cascading failures through the members of a shard. |
| Comments |
| Comment by Kaloian Manassiev [ 30/Aug/19 ] |
|
Like kevin.pulo explained, there is already a feature like this which allows retries to be disabled, which was implemented as part of I am closing this ticket, because we are not willing to implement a configurable number of retries. |