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 explainer #7340

Closed
beckettsean opened this issue Sep 21, 2016 · 2 comments
Closed

query explainer #7340

beckettsean opened this issue Sep 21, 2016 · 2 comments
Labels
area/queries difficulty/high This issue needs to be broken down into smaller units of work. kind/feature-request

Comments

@beckettsean
Copy link
Contributor

Feature Request

Proposal:

A new query clause, EXPLAIN. When included, the query is not actually run, but the index is checked and TSM files are scanned to determine:

  • number of points queried
  • number of TSM files queried
  • number of shard groups queried
  • lower bound on required RAM for running the query (we can at least determine how many iterators would be needed, and then add some padding for string length) This would not be precise at all, just a helpful relative number.

Current behavior:

There is no way to estimate before running a query how many resources it needs, other than reference to past experience with the same data set.

Desired behavior:

Use case: [Why is this important (helps with prioritizing requests)]

Users can have some idea whether a query will succeed before running it and potentially OOM-ing the system.

@beckettsean
Copy link
Contributor Author

#7341 is probably a good first step

@jsternberg jsternberg added area/queries difficulty/high This issue needs to be broken down into smaller units of work. kind/feature-request labels Sep 21, 2016
@jsternberg
Copy link
Contributor

This was done in #8776 and #8947.

@ghost ghost removed the in progress label Jan 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/queries difficulty/high This issue needs to be broken down into smaller units of work. kind/feature-request
Projects
None yet
Development

No branches or pull requests

3 participants