Hello there,   Director uses Cloudera Manager's API under the hood to configure services. The selection of parameters supported for HBase can be found here.   http://www.cloudera.com/documentation/enterprise/properties/5-8-x/topics/cm_props_cdh580_hbase.html   You can include the parameters you need in service or role configurations specified through Director, either in the UI or in a configuration file. Use the name in the "API" column of the page linked above to name each property. For example, to specify the region server message interval, include the "hbase_regionserver_msginterval" configuration property in the role configuration for region servers. A configuration file would specify it like this, perhaps in an "workers" instance group.   roles {   ...   HBASE: [REGIONSERVER]   ... } configs {   HBASE {     REGIONSERVER {       hbase_regionserver_msginterval: 10     }   } }   Take a look at the sample configuration files shipped with Director for a complete example.   https://www.cloudera.com/documentation/director/latest/topics/director_cluster_config.html   General documentation about setting these kinds of configuration properties is here:   https://www.cloudera.com/documentation/director/latest/topics/director_setting_cm_configs.html ... View more

All,   We can set the parameters if we do the following and it was a tough lesson to learn..   There is a config session for Service wide parameters and then for specific areas, do not list or mix which parameters exist for which session as it will throw an error, but not an intelligent one.    Additionally, I would recommend before setting parameters to run the script to dump the entire configuration into a file and then to review the specific parameters and the naming of them.  I was using the GUI and seeing items like HBASE.replication and thought that this could be used, which was not the case.  Instead, it was HBASE_enable_replication.   I also found what I believe was a naming issue in that the name of the parameter did not align with the value, it wasn't spelled correctly like "..ion" and was "..on".  The problem was I was spelling according to english vs reviewing the parameter name.     ... View more