Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 9 Oct 2014 23:32:34 +0000 (UTC)
From: "Sandy Ryza (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12730143.1406530715000.232928.1412897554078@Atlassian.JIRA>
In-Reply-To: <JIRA.12730143.1406530715000@Atlassian.JIRA>
References: <JIRA.12730143.1406530715000@Atlassian.JIRA>
 <JIRA.12730143.1406530715609@arcas>
Subject: [jira] [Commented] (MAPREDUCE-6009) Map-only job with new-api runs
 wrong OutputCommitter when cleanup scheduled in a reduce slot
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sandy Ryza commented on MAPREDUCE-6009:
---------------------------------------

Is this an issue in Hadoop 2 as well?

> Map-only job with new-api runs wrong OutputCommitter when cleanup scheduled in a reduce slot
> --------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6009
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6009
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client, job submission
>    Affects Versions: 1.2.1
>            Reporter: Gera Shegalov
>            Assignee: Gera Shegalov
>            Priority: Blocker
>         Attachments: MAPREDUCE-6009.v01-branch-1.2.patch
>
>
> In branch 1 job commit is executed in a JOB_CLEANUP task that may run in either map or reduce slot
> in org.apache.hadoop.mapreduce.Job#setUseNewAPI there is a logic setting new-api flag only for reduce-ful jobs.
> {code}
>     if (numReduces != 0) {
>       conf.setBooleanIfUnset("mapred.reducer.new-api",
>                              conf.get(oldReduceClass) == null);
>       ...
> {code}
> Therefore, when cleanup runs in a reduce slot, ReduceTask inits using the old API and runs incorrect default OutputCommitter, instead of consulting OutputFormat.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)