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

Hudson commented on MAPREDUCE-6277:
-----------------------------------

FAILURE: Integrated in Hadoop-Hdfs-trunk #2069 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/2069/])
MAPREDUCE-6277. Job can post multiple history files if attempt loses connection 
to the RM. Contributed by Chang Li (jlowe: rev 
30da99cbaf36aeef38a858251ce8ffa5eb657b38)
* 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/rm/TestRMContainerAllocator.java
* 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java
* hadoop-mapreduce-project/CHANGES.txt


> Job can post multiple history files if attempt loses connection to the RM
> -------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6277
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6277
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mr-am
>    Affects Versions: 2.7.0
>            Reporter: Chang Li
>            Assignee: Chang Li
>             Fix For: 2.7.0
>
>         Attachments: MAPREDUCE-6277.2.patch, MAPREDUCE-6277.patch, 
> 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