[
https://issues.apache.org/jira/browse/HDFS-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740103#comment-13740103
]
Kai Zheng commented on HDFS-5087:
---------------------------------
In hdfs script, with the following line
{code}
exec "$JAVA" -Dproc_$COMMAND $JAVA_HEAP_MAX $HADOOP_OPTS $CLASS "
{code}
If both JAVA_HEAP_MAX and service specific -Xmx (via relevant *_OPTS) are set,
then which one will be used? JAVA_HEAP_MAX is always defined in
hadoop-config.sh. Even JVM has clear definition about it, IMO it would be
better to avoid it. The way used in the patch to resolve the conflict
considered to be consistent with YARN related services.
> Allowing specific JAVA heap max setting for HDFS related services
> -----------------------------------------------------------------
>
> Key: HDFS-5087
> URL: https://issues.apache.org/jira/browse/HDFS-5087
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: scripts
> Reporter: Kai Zheng
> Priority: Minor
> Attachments: HDFS-5087.patch
>
>
> This allows specific JAVA heap max setting for HDFS related services as it
> does for YARN services, to be consistent.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
