hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-10959) Templeton launcher job should reconnect to the running child job on task retry
Date Thu, 11 Jun 2015 04:54:00 GMT


Hive QA commented on HIVE-10959:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 9007 tests executed
*Failed tests:*

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 4 tests failed

This message is automatically generated.

ATTACHMENT ID: 12738939 - PreCommit-HIVE-TRUNK-Build

> Templeton launcher job should reconnect to the running child job on task retry
> ------------------------------------------------------------------------------
>                 Key: HIVE-10959
>                 URL:
>             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

View raw message