[SERVER-5474] abort queries in mongos and mongod when incoming conn dies Created: 02/Apr/12 Updated: 08/Jan/24 Resolved: 18/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Mira Carey |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | platforms-re-triaged | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
... no reason to perform queries when the results won't be used. There may be other op types when this is safe as well. Have a patch for mongos that can interrupt while waiting for results from mongod, mongod could abort when yielding. |
| Comments |
| Comment by Mira Carey [ 18/Dec/17 ] |
|
Given our new emphasis on sessions (and on the ability to resume operations across network failures), this ticket isn't really applicable anymore. |
| Comment by Greg Studer [ 02/Apr/12 ] |
|
ideally this would also help systemic issues when an application times out connections that are taking too long b/c of load. |