hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Chen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-2206) The task-cleanup tasks should be optional
Date Tue, 30 Nov 2010 06:19:11 GMT

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

Scott Chen commented on MAPREDUCE-2206:
---------------------------------------

The other problem we have observed is that task-cleanup tasks always go to the same node as
the failed tasks.
This is bad because it may go to the same bad node.
We have seen many times that a task and its cleanup tasks both got timeout on same node.

> The task-cleanup tasks should be optional
> -----------------------------------------
>
>                 Key: MAPREDUCE-2206
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2206
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobtracker
>    Affects Versions: 0.23.0
>            Reporter: Scott Chen
>            Assignee: Scott Chen
>             Fix For: 0.23.0
>
>
> For job does not use OutputCommitter.abort(), this should be able to turn off.
> This improves the latency of the job because failed tasks are often the bottleneck of
the jobs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message