You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Zoltán Borók-Nagy (Jira)" <ji...@apache.org> on 2019/12/12 10:51:00 UTC

[jira] [Created] (IMPALA-9239) Add timeout for query analysis/planning

Zoltán Borók-Nagy created IMPALA-9239:
-----------------------------------------

             Summary: 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


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)