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

Hudson commented on MAPREDUCE-5009:
-----------------------------------

Integrated in Hadoop-Yarn-trunk #133 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/133/])
    MAPREDUCE-5009. Killing the Task Attempt slated for commit does not clear 
the value from the Task commitAttempt member (Robert Parker via jeagles) 
(Revision 1447965)

     Result = SUCCESS
jeagles : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1447965
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/job/impl/TaskImpl.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/job/impl/TestTaskImpl.java

                
> Killing the Task Attempt slated for commit does not clear the value from the 
> Task commitAttempt member
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5009
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5009
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv1
>    Affects Versions: trunk, 2.0.3-alpha, 0.23.5
>            Reporter: Robert Parker
>            Assignee: Robert Parker
>            Priority: Critical
>             Fix For: 3.0.0, 0.23.7, 2.0.4-beta
>
>         Attachments: MAPREDUCE-5009_branch23.patch, MAPREDUCE-5009.patch
>
>
> A reduce task attempt was killed by the RM(pre-emptively), but had already 
> been assigned to the commitAttempt member.  This causes all subsequent 
> attempts to be killed by the AM.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to