hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-10959) Templeton launcher job should reconnect to the running child job on task retry
Date Thu, 11 Jun 2015 06:52:00 GMT

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

Thejas M Nair commented on HIVE-10959:
--------------------------------------

The test failures are unrelated.


> 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.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)

Mime
View raw message