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

Hudson commented on MAPREDUCE-4425:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #1256 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1256/])
    MAPREDUCE-4425. Speculation + Fetch failures can lead to a hung job (jlowe 
via bobby) (Revision 1408360)

     Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1408360
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

                
> Speculation + Fetch failures can lead to a hung job
> ---------------------------------------------------
>
>                 Key: MAPREDUCE-4425
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4425
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.1
>            Reporter: Siddharth Seth
>            Assignee: Jason Lowe
>            Priority: Critical
>             Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
>         Attachments: MAPREDUCE-4425-branch23.patch, MAPREDUCE-4425.patch, 
> MAPREDUCE-4425.patch
>
>
> After a task goes to SUCCEEDED, FAILED/KILLED attempts are ignored.
> 1. attemp1 starts
> 2. speculative attempt starts
> 3. attempt 1 completes - Task moves to SUCCEEDED state
> 4. speculative attempt is KILLED
> 5. T_ATTEMPT_KILLED is ignored.
> 6. attemp1 1 fails with TOO_MANY_FETCH_FAILURES
> The job will effectively hang, since a new task attempt isn't started.

--
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