[
https://issues.apache.org/jira/browse/HBASE-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885749#action_12885749
]
Jean-Daniel Cryans commented on HBASE-2817:
-------------------------------------------
In hbase-env.sh we have this which looks like what Hadoop has:
{code}
# export HBASE_JMX_BASE="-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false"
# export HBASE_MASTER_OPTS="$HBASE_MASTER_OPTS $HBASE_JMX_BASE
-Dcom.sun.management.jmxremote.port=10101"
# export HBASE_REGIONSERVER_OPTS="$HBASE_REGIONSERVER_OPTS $HBASE_JMX_BASE
-Dcom.sun.management.jmxremote.port=10102"
# export HBASE_THRIFT_OPTS="$HBASE_THRIFT_OPTS $HBASE_JMX_BASE
-Dcom.sun.management.jmxremote.port=10103"
# export HBASE_ZOOKEEPER_OPTS="$HBASE_ZOOKEEPER_OPTS $HBASE_JMX_BASE
-Dcom.sun.management.jmxremote.port=10104"
{code}
The -Xmx's kinda already easy to add this way. You want to break it out even
more?
> Allow separate HBASE_REGIONSERVER_HEAPSIZE and HBASE_MASTER_HEAPSIZE
> --------------------------------------------------------------------
>
> Key: HBASE-2817
> URL: https://issues.apache.org/jira/browse/HBASE-2817
> Project: HBase
> Issue Type: Improvement
> Components: scripts
> Affects Versions: 0.21.0
> Reporter: Todd Lipcon
> Priority: Minor
>
> Right now we have a single HBASE_HEAPSIZE configuration. This isn't that
> great, since the HMaster doesn't really need much ram compared to the region
> servers. We should allow different java options and heapsize for the
> different daemon types.
> Probably worth breaking out THRIFT, REST, AVRO, etc, as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
