You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Ivan Mitic (JIRA)" <ji...@apache.org> on 2015/06/11 18:06:00 UTC
[jira] [Commented] (HIVE-10959) webhcat launcher job should
reconnect to the running child job on task retry
[ https://issues.apache.org/jira/browse/HIVE-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582156#comment-14582156 ]
Ivan Mitic commented on HIVE-10959:
-----------------------------------
Thanks [~thejas] for the review and commit!
> webhcat launcher job should reconnect to the running child job on task retry
> ----------------------------------------------------------------------------
>
> Key: HIVE-10959
> URL: https://issues.apache.org/jira/browse/HIVE-10959
> Project: Hive
> Issue Type: Bug
> Components: WebHCat
> Affects Versions: 0.15.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Fix For: 1.2.1
>
> Attachments: HIVE-10959.2.patch, HIVE-10959.3.patch, HIVE-10959.4.patch, HIVE-10959.patch
>
>
> Currently, Templeton launcher kills all child jobs (jobs tagged with the parent job's id) upon task retry.
> Upon templeton launcher task retry, templeton should reconnect to the running job and continue tracking its progress that way.
> This logic cannot be used for all job kinds (e.g. for jobs that are driven by the client side like regular hive). However, for MapReduceV2, and possibly Tez and HiveOnTez, this should be the default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)