You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "radford nguyen (JIRA)" <ji...@apache.org> on 2019/07/08 04:45:00 UTC
[jira] [Updated] (IMPALA-8571) Make query-hook-execution more
robust and observable
[ https://issues.apache.org/jira/browse/IMPALA-8571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
radford nguyen updated IMPALA-8571:
-----------------------------------
Description:
The execution of \{{QueryEventHook}}s currently has some drawbacks in the design:
* exceptions thrown from hooks are simply logged by the Frontend and ignored
* hooks that hang will forever block an executor thread (currently fixed-size threadpool)
* an unbounded queue is used for scheduled hook tasks, which means that slow/hanging hooks may cause the queue to grow and grow until an {{OutOfMemoryError}} is thrown
* metrics around hook execution are not captured (which would really help in debugging/diagnosis)
These are all points that should be addressed/improved in this ticket
h3. Code Review: [https://gerrit.cloudera.org/c/13748/]
was:
The execution of {{QueryEventHook}}s currently has some drawbacks in the design:
* exceptions thrown from hooks are simply logged by the Frontend and ignored
* hooks that hang will forever block an executor thread (currently fixed-size threadpool)
* an unbounded queue is used for scheduled hook tasks, which means that slow/hanging hooks may cause the queue to grow and grow until an {{OutOfMemoryError}} is thrown
* metrics around hook execution are not captured (which would really help in debugging/diagnosis)
These are all points that should be addressed/improved in this ticket
> Make query-hook-execution more robust and observable
> ----------------------------------------------------
>
> Key: IMPALA-8571
> URL: https://issues.apache.org/jira/browse/IMPALA-8571
> Project: IMPALA
> Issue Type: Sub-task
> Components: Frontend
> Reporter: radford nguyen
> Assignee: radford nguyen
> Priority: Major
>
> The execution of \{{QueryEventHook}}s currently has some drawbacks in the design:
> * exceptions thrown from hooks are simply logged by the Frontend and ignored
> * hooks that hang will forever block an executor thread (currently fixed-size threadpool)
> * an unbounded queue is used for scheduled hook tasks, which means that slow/hanging hooks may cause the queue to grow and grow until an {{OutOfMemoryError}} is thrown
> * metrics around hook execution are not captured (which would really help in debugging/diagnosis)
> These are all points that should be addressed/improved in this ticket
> h3. Code Review: [https://gerrit.cloudera.org/c/13748/]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org