Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query Management Support #5939

Closed
jwilder opened this issue Mar 8, 2016 · 2 comments
Closed

Query Management Support #5939

jwilder opened this issue Mar 8, 2016 · 2 comments
Assignees

Comments

@jwilder
Copy link
Contributor

jwilder commented Mar 8, 2016

This is a tracking issue for discussion related to query management. See #655 #654 #5838.

@jsternberg
Copy link
Contributor

I've gotten support for displaying running queries with SHOW QUERIES and modified the query language to allow saying KILL QUERY <number>, but the second isn't fully implemented in a way that works well.

First, in the current query engine, the interrupt will only take place after the first row gets emitted (name/tag combination). It also will not interrupt in the middle of calculating a query. We might have to add interrupt points inside of the iterator to get this functionality to interrupt a count in the middle of calculation, but that may result in slower aggregations.

I'll have to benchmark some attempts to see what happens.

@jwilder
Copy link
Contributor Author

jwilder commented Mar 16, 2016

Related to query limits: #6024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants