Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Mon, 8 Jun 2015 05:42:00 +0000 (UTC)
From: "Ivan Mitic (JIRA)" <jira@apache.org>
To: dev@hive.apache.org
Message-ID: <JIRA.12836063.1433742069000.14349.1433742120615@Atlassian.JIRA>
In-Reply-To: <JIRA.12836063.1433742069000@Atlassian.JIRA>
References: <JIRA.12836063.1433742069000@Atlassian.JIRA>
 <JIRA.12836063.1433742069825@arcas>
Subject: [jira] [Created] (HIVE-10959) Templeton launcher job should
 reconnect to the running child job on its task retry when RMHA is enabled
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ivan Mitic created HIVE-10959:
---------------------------------

             Summary: Templeton launcher job should reconnect to the running child job on its task retry when RMHA is enabled
                 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


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)