[SERVER-9645] Have Mongos handle connection exceptions to shards internally Created: 10/May/13 Updated: 06/Dec/22 Resolved: 12/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Hows | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Sharding
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
Currently if there is a connection exception when running a query on a MongoS the connection exception will be returned to the client as the query failed. We should look at having these exceptions handled internally and if possible retry the query. |
| Comments |
| Comment by Gregory McKeon (Inactive) [ 12/Jul/18 ] |
|
With retryable writes and auto-retry logic in the drivers and mongos, this has gone away. |
| Comment by David Hows [ 10/May/13 ] |
|
Steps to reproduce.
|