[jira] [Updated] (HBASE-17426) Inconsistent environment variable names for enabling JMX

["Chia-Ping Tsai (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-17426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chia-Ping Tsai updated HBASE-17426:
-----------------------------------
    Fix Version/s: 1.4.0
                   2.0.0

> 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
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-17426.v0.patch
>
>
> 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.15#6346)