hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-15441) Provide a config to timeout long compiling queries
Date Tue, 03 Jan 2017 20:29:58 GMT

    [ https://issues.apache.org/jira/browse/HIVE-15441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796099#comment-15796099
] 

Sergey Shelukhin commented on HIVE-15441:
-----------------------------------------

I think the only way to achieve this would be to add interrupt checks on case by case basis.
Talking to remote metastore or metastore DB should be blocking, right? So at least the network
call will be interrupted, and hopefully won't just lead to retry, undecipherable errors or
some other such nonsense typical of the Hive exception handing :)

> Provide a config to timeout long compiling queries
> --------------------------------------------------
>
>                 Key: HIVE-15441
>                 URL: https://issues.apache.org/jira/browse/HIVE-15441
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Planning
>            Reporter: Chao Sun
>            Assignee: Chao Sun
>         Attachments: HIVE-15441.1.patch
>
>
> Sometimes Hive users have long compiling queries which may need to scan thousands or
even more partitions (perhaps by accident). The compilation process may take a very long time,
especially in {{getInputSummary}} where it need to make NN calls to get info about each input
path.
> This is bad because it may block many other queries. Parallel compilation may be useful
but still {{getInputSummary}} has a global lock. In this case, it makes sense to provide Hive
admin with a config to put a timeout limit for compilation, so that these "bad" queries can
be blocked.
> Note https://issues.apache.org/jira/browse/HIVE-12431 also tries to address similar issue.
However it cancels those queries that are waiting for the compile lock, which I think is not
so useful for our case since the *query under compile is the one to be blamed.*



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message