hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HADOOP-5547) One bad node can cause whole job to fail
Date Thu, 11 Aug 2011 18:10:32 GMT

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

Eli Collins resolved HADOOP-5547.

    Resolution: Won't Fix

Out of date

> One bad node can cause whole job to fail
> ----------------------------------------
>                 Key: HADOOP-5547
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5547
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Nathan Marz
> This happened on the 0.19.2 branch. One of the nodes in our cluster was having disk problems
and every task run on it was failing. In general the node would get blacklisted and jobs would
run fine on it. However, for one job, the job ran the "Job setup" task on this bad node. When
the task failed, the task was then retried on the same bad node 3 more times until the job
failed. Hadoop should be able to handle this situation better.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message