[
https://issues.apache.org/jira/browse/HIVE-15441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764427#comment-15764427
]
Chaoyu Tang commented on HIVE-15441:
------------------------------------
[~csun] I think the time and frequency to check the interrupt signal might be
quite important. Also Hive should gracefully stop the services (e.g. HMS) and
release resources when stopping the process.
> 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)
