Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 12 Nov 2012 18:03:13 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <691781105.101580.1352743393833.JavaMail.jiratomcat@arcas>
In-Reply-To: <1524650415.30372.1341947314847.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (MAPREDUCE-4425) Speculation + Fetch failures
 can lead to a hung job
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hadoop QA commented on MAPREDUCE-4425:
--------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12553144/MAPREDUCE-4425-branch23.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3015//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-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