Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <18071013.1181943086058.JavaMail.jira@brutus>
Date: Fri, 15 Jun 2007 14:31:26 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-1472) Timed-out tasks are marked as
 'KILLED' rather than as 'FAILED' which means the framework doesn't fail a
 TIP with 4 or more timed-out attempts
In-Reply-To: <13915888.1181245047180.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Cutting updated HADOOP-1472:
---------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I just committed this.  Thanks, Arun!

> Timed-out tasks are marked as 'KILLED' rather than as 'FAILED' which means the framework doesn't fail a TIP with 4 or more timed-out attempts
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1472
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1472
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.13.0
>            Reporter: Arun C Murthy
>            Assignee: Arun C Murthy
>            Priority: Blocker
>             Fix For: 0.14.0
>
>         Attachments: HADOOP-1472_1_20070608.patch, HADOOP-1472_2_20070608.patch, HADOOP-1472_3_20070612.patch
>
>
> Timed-out tasks (and also tasks which fail with {{FSError}}) are marked as {{KILLED}} rather than as {{FAILED}}. The major issue with this is that post HADOOP-1050 only {{FAILED}} task-attempts are considered to decide if the {{TIP}} has failed, and hence there exists a corner case where a {{TIP}} which has 4 timed-out tasks isn't marked as {{FAILED}} and thus the job keeps running too...
> Considering this is a corner-case and is going to entail not-too-insignificant changes to {{TaskTracker}}'s control-flow (ugly as it is right now), I'm proposing to fix this either for 0.13.1 (if need be) or better: 0.14.
> Thoughts?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.