You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Scott Chen (JIRA)" <ji...@apache.org> on 2011/01/03 19:28:46 UTC

[jira] Commented: (MAPREDUCE-2207) Task-cleanup task should not be scheduled on the node that the task just failed

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976858#action_12976858 ] 

Scott Chen commented on MAPREDUCE-2207:
---------------------------------------

Hi Liyin,
Sorry for the late reply. I think it is OK to call hasFailedAndNeedCleanupTask(). Compared to other things we do in a heartbeat, this one should be OK.
What do you think?

The last patch looks good to me. I just have a nitpick.
Can we change the name of the method hasFailedAndNeedCleanupTask() to hasFailedUncleanTask() ?

> 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, 2207-2.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.