hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ChiaPing Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17426) Inconsistent environment variable names for enabling JMX
Date Sat, 14 Jan 2017 18:10:26 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822893#comment-15822893
] 

ChiaPing Tsai commented on HBASE-17426:
---------------------------------------

Can i take this issue? Which one is better? Should the document be updated in the patch?

> 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)

Mime
View raw message