You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/05/08 19:52:02 UTC

[jira] [Resolved] (MAPREDUCE-97) Increase map/reduce child tasks' heapsize from current default of 200M to 512M

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

Vinod Kumar Vavilapalli resolved MAPREDUCE-97.
----------------------------------------------
    Resolution: Invalid

Very old JIRA.

With MRv2, we have largely also moved _away_ from default Xmx values.

Closing this as invalid.

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)