[
https://issues.apache.org/jira/browse/HADOOP-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641340#action_12641340
]
Amareshwari Sriramadasu commented on HADOOP-4305:
-------------------------------------------------
Another question : Does the restart of a task tarcker say it is healthy? Or
should we make admin explicitly say that the task tracker is healthy?
bq. Irrespective of all this, Map/Reduce should have a utility similar to
dfsadmin -refreshNodes , to add and delete trackers to cluster anytime.
This could be a separate jira, if it is really required.
> 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.
