[
https://issues.apache.org/jira/browse/MAPREDUCE-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved MAPREDUCE-97.
------------------------------
Resolution: Duplicate
This is sorta being handled via MAPREDUCE-4316 today. However, the -Xmx200m has
served well with io.sort.mb as 100 all these years. Whatever the issue was
here, it had gone away (was some other leak).
Resolving as dupe.
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
