[
https://issues.apache.org/jira/browse/HIVE-10959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14578212#comment-14578212
]
Thejas M Nair commented on HIVE-10959:
--------------------------------------
The jar command executes a java function in the class specified. It is possible
that the command runs more than one MR job (lets say n), and the launcher job
gets killed during a n-x job, the remaining x jobs will not be executed.
But I guess the way things are written in webhcat, (progresss notifcation etc),
it is not written to work with more than one MR job being run by the function
in class specified, so this patch should be fine. Any thoughts on that
[~ivanmi] ?
> Templeton 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
> Attachments: 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)
