Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <29208312.1172020865844.JavaMail.jira@brutus>
Date: Tue, 20 Feb 2007 17:21:05 -0800 (PST)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-654) jobs fail with some hardware/system
 failures on a small number of nodes
In-Reply-To: <12549458.1162234096611.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arun C Murthy updated HADOOP-654:
---------------------------------

    Attachment: HADOOP-654_20070220_3.patch

Updated patch for review...

> jobs fail with some hardware/system failures on a small number of nodes
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-654
>                 URL: https://issues.apache.org/jira/browse/HADOOP-654
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.7.2
>            Reporter: Yoram Arnon
>         Assigned To: Arun C Murthy
>            Priority: Minor
>             Fix For: 0.12.0
>
>         Attachments: HADOOP-654_20070208_1.patch, HADOOP-654_20070209_2.patch, HADOOP-654_20070220_3.patch
>
>
> occasionally, such as when the OS is out of some resource, a node fails only partly. The node is up and running, the task tracker is running and sending heartbeats, but every task fails because the tasktracker can't fork tasks or something.
> In these cases, that task tracker keeps getting assigned tasks to execute, and they all fail.
> A couple of nodes like that and jobs start failing badly.
> The job tracker should avoid assigning tasks to tasktrackers that are misbehaving.
> simple approach: avoid tasktrackers that report many more failures than average (say 3X). Simply use the info sent by the TT.
> better but harder: track TT failures over time and:
>  1. avoid those that exhibit a high failure *rate*
>  2. tell them to shut down

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