[
https://issues.apache.org/jira/browse/MAPREDUCE-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975403#action_12975403
]
Liyin Liang commented on MAPREDUCE-2207:
----------------------------------------
Hi Scott,
If we move this logic to server side, every heartbeat has to call
hasFailedAndNeedCleanupTaskToReport() inside the lock of JobTracker. Is there
be a performance loss of jt?
> Task-cleanup task should not be scheduled on the node that the task just
> failed
> -------------------------------------------------------------------------------
>
> Key: MAPREDUCE-2207
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2207
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobtracker
> Affects Versions: 0.23.0
> Reporter: Scott Chen
> Fix For: 0.23.0
>
> Attachments: 0.19.1.diff, 2207-1.diff
>
>
> Currently the task-cleanup task always go to the same node that the task just
> failed.
> There is a higher chance that it hits a bad node. This should be changed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
