[
https://issues.apache.org/jira/browse/HDFS-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740414#comment-13740414
]
Kai Zheng commented on HDFS-5087:
---------------------------------
bq.just process the command line parameters and strip duplicates?
Rather than do some post fix like this, wouldn't we have a consistent approach?
Why introduce JAVA_HEAP_MAX? Either respect it always or discard it I would
think.
bq.That won't scale.
I'm wondering if it's a good practice to add many application options and
parameters like logging stuff via -D to JAVA command line.
> 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
