Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <15584050.18691291098192045.JavaMail.jira@thor>
Date: Tue, 30 Nov 2010 01:23:12 -0500 (EST)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-2206) The task-cleanup tasks should be
 optional
In-Reply-To: <1659385.18451291097530753.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

dhruba borthakur commented on MAPREDUCE-2206:
---------------------------------------------

from my understanding, the cleanup task is machine specific and is *supposed* to go to the same machine where the user's task was run. Maybe a mapred guru can clarify this. 

> 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.