[
https://issues.apache.org/jira/browse/HBASE-12309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell resolved HBASE-12309.
-----------------------------------------
Resolution: Duplicate
> Customize Java Heap min/max settings for individual processes
> -------------------------------------------------------------
>
> Key: HBASE-12309
> URL: https://issues.apache.org/jira/browse/HBASE-12309
> Project: HBase
> Issue Type: Improvement
> Components: master, regionserver, REST
> Affects Versions: 0.98.5, 0.99.1
> Reporter: Mark Tse
> Priority: Minor
> Labels: heap, java, master, regionserver, rest
>
> The separate processes (master, regionserver, zookeeper, rest, etc.) all run
> using $JAVA_HEAP_MAX in 'bin/hbase'. However, there may be cases where we
> want the processes to run with different Java max heap sizes.
> In 0.98.5, HBASE_(.*)_OPTS variables exist for these processes and can be
> used to add the Xms and Xmx tags, but because of how the default for
> JAVA_HEAP_MAX is set, it will always add '-Xmx1000m' to the final call to
> start up the master/regionserver/rest process, resulting in two different
> Java heap settings (e.g. -Xmx1000m and -Xmx8g is used when starting the
> master).
> In 0.99.1, this default no longer exists so HBASE_(.*)_OPTS is usable, but it
> would be nice to have dedicated variables for each process.
> This issue also exists in Hadoop HDFS ([HDFS-7255]).
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
