I am not sure what 'FA' means in this context, but CM APIs offer license information via the following REST end-points: http://cloudera.github.io/cm_api/apidocs/v18/path__cm_license.html http://cloudera.github.io/cm_api/apidocs/v18/path__cm_licensedFeatureUsage.html An example query: # For licensee details and UIDs: ~> curl -u admin http://cm-hostname.organization.com:7180/api/v18/cm/license … { "owner" : "Licensee Name", "uuid" : "12345678-abcd-1234-abcd-1234abcd1234" } # For license usage details: ~> curl -u admin http://cm-hostname.organization.com:7180/api/v18/cm/licensedFeatureUsage … { "totals" : { "Core" : 8, "HBase" : 8, "Impala" : 8, "Search" : 5, "Spark" : 3, "Accumulo" : 4, "Navigator" : 8 }, "clusters" : { "Cluster 1" : { "Core" : 4, "HBase" : 4, "Impala" : 4, "Search" : 4, "Spark" : 2, "Accumulo" : 4, "Navigator" : 4 }, "Cluster 2" : { "Core" : 4, "HBase" : 4, "Impala" : 4, "Search" : 1, "Spark" : 1, "Accumulo" : 0, "Navigator" : 4 } } } ... View more

A bit of info: - total_read_requests_rate_across_regionservers tracks the RS JMX bean of Server::readRequestCount - total_write_requests_rate_across_regionservers tracks the RS JMX bean of Server::writeRequestCount - total_requests_rate_across_regionservers tracks the RS JMX bean of Server::totalRequestCount The first two apply only to RS operations that operate on data, but the third applies also to other meta-operations such as openRegion, closeRegion, etc. that the RegionServer services (for Master and other commanding clients). > Which metric reflects the actual load of the HBase cluster? Data-wise its the read/write requests you want to look at. > Given the names I was expecting something like: total_requests = total_read_requests + total_write_requests but this is clearly not the case. The readRequestCount tracks only read operations (get/scan), where it also counts up multiple rows counted during scans. The totalRequestCount only counts by one per RPC done to RS, not per-row of reads done. This would cause a difference between the three metrics. Hope this helps explain what these three metrics truly are. TL;DR: total_read_requests_rate_across_regionservers -> Read operations count rate, counted per row scanned total_write_requests_rate_across_regionservers -> Write operations count rate, counted per row written total_requests_rate_across_regionservers -> Overall RS RPC-level call count rate, counted per request made to RS, not row-level ... View more

The command is only for non-Cloudera-Manager deployments like the documentation notes: """ In non-managed deployments, you can start a Lily HBase Indexer Daemon manually on the local host with the following command: sudo service hbase-solr-indexer restart """ If you use Cloudera Manager then just add a new Service from the Clusters page of the type "Key-Value Store Indexer" shown in the new service list. Then proceed with configuring it from CM and starting it. ... View more