[
https://issues.apache.org/jira/browse/HBASE-17426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822961#comment-15822961
]
Ted Yu commented on HBASE-17426:
--------------------------------
We should continue to support HBASE_JMX_OPTS - some users may have used it.
In bin/hbase-config.sh, we should also check the value of HBASE_JMX_BASE:
* if value for HBASE_JMX_BASE is empty, keep current behavior.
* if HBASE_JMX_OPTS is not empty, keep current behavior.
* otherwise use the value of HBASE_JMX_BASE
> Inconsistent environment variable names for enabling JMX
> --------------------------------------------------------
>
> Key: HBASE-17426
> URL: https://issues.apache.org/jira/browse/HBASE-17426
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
>
> In conf/hbase-env.sh :
> {code}
> # export HBASE_JMX_BASE="-Dcom.sun.management.jmxremote.ssl=false
> -Dcom.sun.management.jmxremote.authenticate=false"
> # If you want to configure BucketCache, specify '-XX: MaxDirectMemorySize='
> with proper direct memory size
> # export HBASE_THRIFT_OPTS="$HBASE_JMX_BASE
> -Dcom.sun.management.jmxremote.port=10103"
> {code}
> But in bin/hbase-config.sh , a different variable is used:
> {code}
> # Thrift JMX opts
> if [ -n "$HBASE_JMX_OPTS" ] && [ -z "$HBASE_THRIFT_JMX_OPTS" ]; then
> HBASE_THRIFT_JMX_OPTS="$HBASE_JMX_OPTS
> -Dcom.sun.management.jmxremote.port=10103"
> fi
> {code}
> The variable names should be aligned for better user experience.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
