[
https://issues.apache.org/jira/browse/HADOOP-10759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089314#comment-14089314
]
Allen Wittenauer commented on HADOOP-10759:
-------------------------------------------
After a bit more thinking about this idea, I have a proposal to make that I
think will accomplish the ultimate goal of this JIRA while also giving the
users much more control than they have now (a win-win):
# We introduce HADOOP_HEAPSIZE_MAX and HADOOP_HEAPSIZE_MIN, both default to
empty. They will set the Xmx and Xms values, respectively. Both require units
to be provided, such that e.g. HADOOP_HEAPSIZE_MAX="10g" is valid.
# We deprecate HADOOP_HEAPSIZE and JAVA_HEAP_MAX and completely remove them
from the hadoop-env.sh, etc. documentation. The code should honor them if set
(thereby providing backwards compatibility), but the HADOOP_HEAPSIZE_xyz vars
take precedence in case of a conflict.
# I'm willing to do this work as either part of HADOOP-9902 (which rewrites all
of this code anyway) or as part of the series of follow-on patches to that
change, depending upon the review for 9902.
Thoughts?
> 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)
