[
https://issues.apache.org/jira/browse/HIVE-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032115#comment-14032115
]
Romain Rigaux commented on HIVE-7198:
-------------------------------------
Nice! Will have a try!
> HiveServer2 CancelOperation does not work for long running queries
> ------------------------------------------------------------------
>
> Key: HIVE-7198
> URL: https://issues.apache.org/jira/browse/HIVE-7198
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 0.12.0
> Reporter: Romain Rigaux
>
> Sending the CancelOperation() call does not always stop the query and its
> related MapReduce jobs.
> e.g. from https://issues.cloudera.org/browse/HUE-2144
> {code}
> I guess you're right. But the strange thing is that the canceled query shows
> in job browser as 'Running' and the percents go up - 0%, 50%, then the job is
> failed.
> How does the cancelling actually work? Is it like the hadoop kill command? It
> seems to me like it works until certain phase of map reduce is done.
> And another thing - after cancelling the job in Hue I can kill it with hadoop
> job -kill job_<id>. If it was killed already, it would show "no such job".
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
