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

Hadoop QA commented on YARN-3335:
---------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12704859/YARN-3335.2.patch
  against trunk revision ce5de93.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/6981//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6981//console

This message is automatically generated.

> Job In Error State Will Lost Jobhistory Of Second and Later Attempts
> --------------------------------------------------------------------
>
>                 Key: YARN-3335
>                 URL: https://issues.apache.org/jira/browse/YARN-3335
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.7.0
>            Reporter: Chang Li
>            Assignee: Chang Li
>         Attachments: YARN-3335.1.patch, YARN-3335.2.patch
>
>
> Related to a fixed issue MAPREDUCE-6230 which cause a Job to get into error 
> state. In that situation Job's second or some later attempt could succeed but 
> those later attempts' history file will all be lost. Because the first 
> attempt in error state will copy its history file to intermediate dir while 
> mistakenly think of itself as lastattempt. Jobhistory server will later move 
> the history file of that error attempt from intermediate dir to done dir 
> while ignore the rest of that job attempt's later history files in 
> intermediate dir.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to