Cloudera Manager Health Tests
This section provides information on health tests supported by Cloudera Manager.
There are two types of health tests:
- Pass-fail tests - there are two types:
- Compare a property to a yes-no value. For example, whether a service or role started as expected, a DataNode is connected to its NameNode, or a TaskTracker is (or is not) blacklisted.
- Exercise a service lightly to confirm it is working and responsive. HDFS (NameNode role), HBase, and ZooKeeper services perform these tests, which are referred to as "canary" tests.
- Metric tests - compare a property to a numeric value. For example, the number of file descriptors in use, the amount of disk space used or free, how much time spent in garbage collection, or how many pages were swapped to disk in the previous 15 minutes. In these tests the property is compared to a threshold that determine whether everything is Good, (for example, plenty of disk space available), whether it is Concerning (disk space getting low), or is Bad (a critically low amount of disk space).
By default most health tests are enabled and (if appropriate) configured with reasonable thresholds. You can modify threshold values by editing the monitoring properties under the entity's Configuration tab. You can also enable or disable individual or summary health tests, and in some cases specify what should be included in the calculation of overall health for the service, role instance, or host. See Configuring Monitoring Settings for more information.
Continue reading:
- Active Database Health Tests
- Active Key Trustee Server Health Tests
- Activity Monitor Health Tests
- Alert Publisher Health Tests
- Beeswax Server Health Tests
- Cloudera Management Service Health Tests
- DataNode Health Tests
- DSSD DataNode Health Tests
- Event Server Health Tests
- Failover Controller Health Tests
- Flume Health Tests
- Flume Agent Health Tests
- Garbage Collector Health Tests
- HBase Health Tests
- HBase REST Server Health Tests
- HBase Thrift Server Health Tests
- HDFS Health Tests
- History Server Health Tests
- Hive Health Tests
- Hive Metastore Server Health Tests
- HiveServer2 Health Tests
- Host Health Tests
- Host Monitor Health Tests
- HttpFS Health Tests
- Hue Health Tests
- Hue Server Health Tests
- Impala Health Tests
- Impala Catalog Server Health Tests
- Impala Daemon Health Tests
- Impala Llama ApplicationMaster Health Tests
- Impala StateStore Health Tests
- JobHistory Server Health Tests
- JobTracker Health Tests
- JournalNode Health Tests
- Kafka Health Tests
- Kafka Broker Health Tests
- Kafka MirrorMaker Health Tests
- Kerberos Ticket Renewer Health Tests
- Key Management Server Health Tests
- Key Management Server Proxy Health Tests
- Key-Value Store Indexer Health Tests
- Lily HBase Indexer Health Tests
- Load Balancer Health Tests
- Logger Health Tests
- MapReduce Health Tests
- Master Health Tests
- Monitor Health Tests
- NFS Gateway Health Tests
- NameNode Health Tests
- Navigator Audit Server Health Tests
- Navigator HSM KMS Metastore Health Tests
- Navigator HSM KMS Proxy Health Tests
- Navigator Luna KMS Metastore Health Tests
- Navigator Luna KMS Proxy Health Tests
- Navigator Metadata Server Health Tests
- Navigator Thales KMS Metastore Health Tests
- Navigator Thales KMS Proxy Health Tests
- NodeManager Health Tests
- Oozie Health Tests
- Oozie Server Health Tests
- Passive Database Health Tests
- Passive Key Trustee Server Health Tests
- RegionServer Health Tests
- Reports Manager Health Tests
- ResourceManager Health Tests
- SecondaryNameNode Health Tests
- Sentry Health Tests
- Sentry Server Health Tests
- Service Monitor Health Tests
- Solr Health Tests
- Solr Server Health Tests
- Spark Health Tests
- Spark (Standalone) Health Tests
- Spark 2 Health Tests
- Tablet Server Health Tests
- TaskTracker Health Tests
- Telemetry Publisher Health Tests
- Tracer Health Tests
- WebHCat Server Health Tests
- Worker Health Tests
- YARN (MR2 Included) Health Tests
- ZooKeeper Health Tests
- ZooKeeper Server Health Tests