hadoop-mapreduce-issues mailing list archives

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

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

Amareshwari Sriramadasu commented on MAPREDUCE-2206:
----------------------------------------------------

Joydeep is right with analysis. There is no requirement for the task-cleanup to go to the
same machine, because task-cleanup will do cleanup on hdfs. For ex, if the task failed due
lost tracker, it cannot go to the same machine.

> 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