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 "xuzhou (Jira)" <ji...@apache.org> on 2020/01/07 06:13:00 UTC
[jira] [Updated] (IMPALA-9239) Add timeout for query
analysis/planning
[ https://issues.apache.org/jira/browse/IMPALA-9239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
xuzhou updated IMPALA-9239:
---------------------------
Description:
*strong text*We've seen queries hanging in the planner. The concrete hang was in the Kudu client, for that I opened KUDU-3019.
But we should investigate the possibilities of adding an overall timeout on the Frontend activities (analysis/authorization/planning).
It'd be useful because the Frontend reaches out to other services -- e.g. Catalogd, HDFS Namenode, authorization provider, Kudu, etc. --. and an overall timeout would be a robust solution for these kind of hangs in broken API calls.
Of course, in the meantime we should still use timeouts on each API call where possible.
was:
We've seen queries hanging in the planner. The concrete hang was in the Kudu client, for that I opened KUDU-3019.
But we should investigate the possibilities of adding an overall timeout on the Frontend activities (analysis/authorization/planning).
It'd be useful because the Frontend reaches out to other services -- e.g. Catalogd, HDFS Namenode, authorization provider, Kudu, etc. --. and an overall timeout would be a robust solution for these kind of hangs in broken API calls.
Of course, in the meantime we should still use timeouts on each API call where possible.
> Add timeout for query analysis/planning
> ---------------------------------------
>
> Key: IMPALA-9239
> URL: https://issues.apache.org/jira/browse/IMPALA-9239
> Project: IMPALA
> Issue Type: Bug
> Reporter: Zoltán Borók-Nagy
> Priority: Major
>
> *strong text*We've seen queries hanging in the planner. The concrete hang was in the Kudu client, for that I opened KUDU-3019.
> But we should investigate the possibilities of adding an overall timeout on the Frontend activities (analysis/authorization/planning).
> It'd be useful because the Frontend reaches out to other services -- e.g. Catalogd, HDFS Namenode, authorization provider, Kudu, etc. --. and an overall timeout would be a robust solution for these kind of hangs in broken API calls.
> Of course, in the meantime we should still use timeouts on each API call where possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org