[
https://issues.apache.org/jira/browse/MAPREDUCE-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494794#comment-13494794
]
Hadoop QA commented on MAPREDUCE-4425:
--------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12552998/MAPREDUCE-4425.patch
against trunk revision .
{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}. The javadoc tool did not generate any
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 1.3.9) 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.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3009//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3009//console
This message is automatically generated.
> 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
> Attachments: 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
