[
https://issues.apache.org/jira/browse/HADOOP-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644324#action_12644324
]
Christian Kunz commented on HADOOP-4305:
----------------------------------------
I would be happy with Amareshwari's proposal together with Owen's suggestion. I
believe this would help us a lot in our environment.
To only count blacklisted TaskTrackers for successful jobs seems necessary to
avoid false positives because of application issues (although we just had a
case where enough bad-behaving TaskTrackers generated enough individual task
failures to fail jobs repeatedly). Solutions that cover 80% of issues with 20%
of development effort are better than perfect solutions that are never
implemented.
> 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.
