[SERVER-3379] Query Timeout Created: 06/Jul/11 Updated: 29/Aug/11 Resolved: 06/Jul/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 1.8.1 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | David Burley | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
REF: We'd like a sane method to timeout queries. This could be done driver-side; but ideally would be a query-specific option, supported by the server and thus would get picked up by all the drivers as a result for everyone to benefit. We have a few queries that on occasion run too long due to some concurrency related issues around .group(). We wrote a daemon to reap those processes, but it would be much more clean and generally useful to have a generic query timeout that actually kills the query server-side and results in a client-side error than just timing it out at the client and letting the server keep executing. |
| Comments |
| Comment by David Burley [ 06/Jul/11 ] |
|
Indeed it is – thx. Watching the dupe now. |
| Comment by Scott Hernandez (Inactive) [ 06/Jul/11 ] |
|
This is covered in |