You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Arun C Murthy (JIRA)" <ji...@apache.org> on 2009/07/22 23:43:14 UTC

[jira] Resolved: (MAPREDUCE-790) TaskTracker blacklisted by one job should be blacklisted for all other jobs in the queue

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

Arun C Murthy resolved MAPREDUCE-790.
-------------------------------------

    Resolution: Duplicate

See HADOOP-4305 for details on global blacklisting of tasktrackers.

> TaskTracker blacklisted by one job should be blacklisted for all other jobs in the queue
> ----------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-790
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-790
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobtracker
>    Affects Versions: 0.20.1
>            Reporter: Qi Liu
>
> Once a task tracker is blacklisted by one job, it is still being used by all other jobs in the queue. A blacklisted task tracker could be a signal of marginal node, and thus it should be blacklisted for all jobs at least temporarily. Also, even if one task tracker has been blacklisted globally due to too many failures, the blacklists of the jobs in the queue are not affected, and thus will continue to use the bad task tracker. This could result job failure.

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