[
https://issues.apache.org/jira/browse/HADOOP-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644225#action_12644225
]
Devaraj Das commented on HADOOP-4305:
-------------------------------------
Runping, the case we need to consider is faulty tasks (as Koji had pointed out
here -
https://issues.apache.org/jira/browse/HADOOP-4305?focusedCommentId=12641556#action_12641556).
A tasktracker should not stop asking for tasks if the failures were due to
task faults (e.g. buggy user code). So that's why the proposal here is to
increment the blacklist-count for a TT only for successful jobs. If a job
fails, the blacklist-count is not incremented even if the TT got blacklisted
for this job...
> repeatedly blacklisted tasktrackers should get declared dead
> ------------------------------------------------------------
>
> Key: HADOOP-4305
> URL: https://issues.apache.org/jira/browse/HADOOP-4305
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Christian Kunz
> Assignee: Amareshwari Sriramadasu
> Fix For: 0.20.0
>
>
> When running a batch of jobs it often happens that the same tasktrackers are
> blacklisted again and again. This can slow job execution considerably, in
> particular, when tasks fail because of timeout.
> It would make sense to no longer assign any tasks to such tasktrackers and to
> declare them dead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
