[HBASE-17426] Inconsistent environment variable names for enabling JMX

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0, 2.0.0
• Hadoop Flags: Reviewed

Release Note

In bin/hbase-config.sh,
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

• Assignee: Chia-Ping Tsai
• Reporter: Ted Yu
• Created: 04/Jan/17 22:05
• Updated: 17/Mar/17 06:32
• Resolved: 17/Mar/17 02:30

Description

In conf/hbase-env.sh :

# 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"

But in bin/hbase-config.sh , a different variable is used:

# 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

The variable names should be aligned for better user experience.