Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <704357041.1257243959401.JavaMail.jira@brutus>
Date: Tue, 3 Nov 2009 10:25:59 +0000 (UTC)
From: "Amareshwari Sriramadasu (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6357) Reducers fail with OutOfMemoryError
 while copying Map outputs
In-Reply-To: <901610937.1257242879413.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773005#action_12773005 ] 

Amareshwari Sriramadasu commented on HADOOP-6357:
-------------------------------------------------

Sorry, didn't see you previous comment. Please ignore my last comment.

> Reducers fail with OutOfMemoryError while copying Map outputs
> -------------------------------------------------------------
>
>                 Key: HADOOP-6357
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6357
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.20.0
>            Reporter: Chandra Prakash Bhagtani
>             Fix For: 0.20.0
>
>
> Reducers fail while copying Map outputs with following exception
> java.lang.OutOfMemoryError: Java heap space at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.shuffleInMemory(ReduceTask.java:1539) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.getMapOutput(ReduceTask.java:1432) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.copyOutput(ReduceTask.java:1285) at org.apache.hadoop.mapred.ReduceTask$ReduceCopier$MapOutputCopier.run(ReduceTask.java:1216) ,Error:
> Reducer's memory usage keeps on increasing and ultimately exceeds -Xmx value  
> I even tried with -Xmx6.5g to each reducer but it's still failing 
> While looking into the reducer logs, I found that reducers were doing shuffleInMemory every time, rather than doing shuffleOnDisk

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