[
https://issues.apache.org/jira/browse/HADOOP-10759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088817#comment-14088817
]
Eric Yang commented on HADOOP-10759:
------------------------------------
How is removing a hard coded mistake a feature? This is a defect. There is no
need to run with 1GB heap for trivial command line 90% of the time. There is
no contradiction in my statement, it is quote out of context. The 1GB max will
automatically get applied, if no JAVA_HEAP_MAX is defined. However, it should
not cap cli to 1GB in case if an administrator wants to run cli operation that
may require more memory, he can do:
export JAVA_HEAP_MAX=4096m
Then run the cli. distcp and other utilities can directly benefit from this.
YARN hard code is not described in any part of this JIRA, I did not look at
YARN cli that may have the need to remove capped JAVA_HEAP_MAX. If that is
required, it can be filed as another JIRA.
> 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)
