You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2019/06/25 03:48:33 UTC
[GitHub] [incubator-druid] JulianJaffePinterest opened a new issue #7957:
Druid SQL planning time can exceed query timeouts
JulianJaffePinterest opened a new issue #7957: Druid SQL planning time can exceed query timeouts
URL: https://github.com/apache/incubator-druid/issues/7957
### Affected Version
0.14.0-incubating
### Description
Based on our operational experience, Druid SQL query planning can exceed the configured timeout for a query. We've observed this in conjunction with #7904, where requests with large IN clauses (1k+ elements) cause elevated CPU usage on a broker node long after the the query times out. This appears to be due to SqlLifecycle either not respecting query time outs (instead relying on the generated native queries to time out if necessary) or due to the sql planning itself not being cancellable.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org