I am trying to enable tje JVM settings for monitoring of HBase performance. Initially I thought this would be a simple change, but I was wrong.   The documentation briefly mentions that the conf files for Hbase follow Hadoop conventions, but that is probably the case if CDH cluster is installed  directly without the Cloudera manager.   Acorrding to the documentation http://archive.cloudera.com/cdh5/cdh/5/hbase/book.html#jmx_config the hbase-env.sh file should be modified with these settings    export HBASE_JMX_BASE="-Dcom.sun.management.jmxremote.authenticate=true \ -Dcom.sun.management.jmxremote.password.file=your_password_file \ -Dcom.sun.management.jmxremote.access.file=your_access_file" export HBASE_MASTER_OPTS="$HBASE_MASTER_OPTS $HBASE_JMX_BASE " export HBASE_REGIONSERVER_OPTS="$HBASE_REGIONSERVER_OPTS $HBASE_JMX_BASE " The question is which hbase-env.sh should be modified.  The problem is that the CDH agent is dynamically managing the configuration of Hbase, and it seems not to use the /etc/hbase/conf file or  /opt/cloudera/parcels/CDH-5.4.2-1.cdh5.4.2.p0.2/etc/hbase/conf.dist/hbase-env.sh    From what I've seen the CDH client dynamically generates the config file for Supervisord, the process managing Hbase servers, and also the property files under /var/run/cloudera-scm-agent/process/ directory.  Supervisord sets the environment and invokse the Hbase start-up script.    The question is how to overide the settings that normally would go into hbase-env.sh?   I am using CHD 5.4.2 on CentOS 6.6 x86_64, and jdk1.7.0_67   Thanks   Dimitar       ... View more