Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Date: Wed, 17 Oct 2012 05:26:04 +0000 (UTC)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: mapreduce-dev@hadoop.apache.org
Message-ID: <2118234730.55998.1350451564161.JavaMail.jiratomcat@arcas>
Subject: [jira] [Reopened] (MAPREDUCE-97) Increase map/reduce child tasks'
 heapsize from current default of 200M to 512M
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAPREDUCE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun C Murthy reopened MAPREDUCE-97:
------------------------------------


With HDFS-4053 we should revisit this.
                
> Increase map/reduce child tasks' heapsize from current default of 200M to 512M
> ------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-97
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-97
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Arun C Murthy
>            Assignee: Arun C Murthy
>
> I guess we should look to check why we get OOMs with 200M, I'd suspect io.sort.mb hogs a lot of the default 200M. However, HADOOP-1867 should be the right way to solve it. 
> For now, I propose we bump up the child-vm default heapsize to 512M; too many people are getting burnt by 200M.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira