[DOCS-9039] when a socket between mongos and mongod fails, close all connections immediately Created: 28/Sep/16 Updated: 30/Oct/23 Resolved: 24/May/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Emily Hall | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 20 weeks ago | ||||||||
| Description |
|
Currently, mongos closes one connection at a time, even though it can "tell" that every connection to that shard is going to be bad. It could mark them all as failed and so not return as many error to the client. Leads to Assertion: 13633:error querying server errors (for Google-ability). |