[
https://issues.apache.org/jira/browse/HADOOP-10759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang resolved HADOOP-10759.
--------------------------------
Resolution: Fixed
Allen, this JIRA is filed for Hadoop Common, YARN problems can be addressed in
YARN JIRA. The hard coded value was introduced in HADOOP-5212. Before 0.21,
the behavior of JVM heap size control is exactly same as this patch. It does
not look like a new feature if we are just rollback to existing Hadoop behavior
in 2009. We don't need to spread fear on this patch is going to the universe
because it doesn't. This has been tested in stress test, and our clusters have
been running this patch for almost a year before it was contributed to the
community.
> Remove hardcoded JAVA_HEAP_MAX in hadoop-config.sh
> --------------------------------------------------
>
> Key: HADOOP-10759
> URL: https://issues.apache.org/jira/browse/HADOOP-10759
> Project: Hadoop Common
> Issue Type: Bug
> Components: bin
> Affects Versions: 2.4.0
> Environment: Linux64
> Reporter: sam liu
> Priority: Minor
> Fix For: 2.6.0
>
> Attachments: HADOOP-10759.patch, HADOOP-10759.patch
>
>
> In hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh, there
> is a hard code for Java parameter: 'JAVA_HEAP_MAX=-Xmx1000m'. It should be
> removed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
