Hive Metastore Server Health Tests

This Hive Metastore Server health test checks that the Auditing for the Hive Metastore Server role is getting processed correctly and is not blocked. A failure of this health test may indicate a problem with the audit pipeline of Hive Metastore Server process. This test can fail either because the Cloudera Audit Server is not accepting audits, or the Cloudera Manager Agent on the Hive Metastore Server host isn't able to send audits because of some network issue. Check the Cloudera Manager Agent logs and Cloudera Audit Server logs for more details. This test can be enabled or disabled using the Navigator Audit Pipeline Health Check Hive Metastore Server monitoring setting.

Short Name: Audit Pipeline Test

This Hive Metastore Server health test checks that the number of file descriptors used does not rise above some percentage of the Hive Metastore Server file descriptor limit. A failure of this health test may indicate a bug in either Hadoop or Cloudera Manager. Contact Cloudera support. This test can be configured using the File Descriptor Monitoring Thresholds Hive Metastore Server monitoring setting.

Short Name: File Descriptors

This Hive Metastore Server health test checks that the filesystem containing the heap dump directory of this Hive Metastore Server has sufficient free space. This test can be configured using the Heap Dump Directory Free Space Monitoring Absolute Thresholds and Heap Dump Directory Free Space Monitoring Percentage Thresholds Hive Metastore Server monitoring settings.

Short Name: Heap Dump Directory Free Space

The database is created under the /user/hue/.cloudera_manager_hive_metastore_canary/<Hive Metastore role name> / and is named "cloudera_manager_metastore_canary_test_db". The test returns "Bad" health if any of these operations fail. The test returns "Concerning" health if an unknown failure happens. The canary publishes a metric 'canary_duration' for the time it took for the canary to complete. The following example trigger, defined for the Hive Metastore role configuration group, changes the health to "Bad" when the time it takes for the canary to finish the testing tasks is longer than 10 seconds:

"IF (SELECT canary_duration WHERE entityName=$ROLENAME AND category = ROLE and last(canary_duration) > 10s) DO health:bad"

A failure of this health test might indicate that the Hive Metastore is failing basic operations. Check the logs of the Hive Metastore and the Cloudera Manager Service Monitor for more details. This test can be enabled or disabled using the Hive Metastore Canary Health Test Hive Metastore monitoring setting.

Short Name: Hive Metastore Canary

This Hive Metastore Server health test factors in the health of the host upon which the Hive Metastore Server is running. A failure of this test means that the host running the Hive Metastore Server is experiencing some problem. See that host's status page for more details.This test can be enabled or disabled using the Hive Metastore Server Host Health Test Hive Metastore Server monitoring setting.

Short Name: Host Health

This Hive Metastore Server health test checks that the filesystem containing the log directory of this Hive Metastore Server has sufficient free space. This test can be configured using the Log Directory Free Space Monitoring Absolute Thresholds and Log Directory Free Space Monitoring Percentage Thresholds Hive Metastore Server monitoring settings.

Short Name: Log Directory Free Space

This Hive Metastore Server health test checks that the Hive Metastore Server threads are not experiencing long scheduling pauses. The test uses a pause monitoring thread in the Hive Metastore Server that tracks scheduling delay by noting if it is run on its requested schedule. If the thread is not run on its requested schedule, the delay is noted and considered pause time. The health test checks that no more than some percentage of recent time is spent paused. A failure of this health test may indicate that the Hive Metastore Server is not getting enough CPU resources, or that it is spending too much time doing garbage collection. Inspect the Hive Metastore Server logs for any pause monitor output and check garbage collection metrics exposed by the Hive Metastore Server. This test can be configured using the Pause Duration Thresholds and Pause Duration Monitoring Period Hive Metastore Server monitoring settings.

Short Name: Pause Duration

This Hive Metastore Server health test checks that the Cloudera Manager Agent on the Hive Metastore Server host is heart beating correctly and that the process associated with the Hive Metastore Server role is in the state expected by Cloudera Manager. A failure of this health test may indicate a problem with the Hive Metastore Server process, a lack of connectivity to the Cloudera Manager Agent on the Hive Metastore Server host, or a problem with the Cloudera Manager Agent. This test can fail either because the Hive Metastore Server has crashed or because the Hive Metastore Server will not start or stop in a timely fashion. Check the Hive Metastore Server logs for more details. If the test fails because of problems communicating with the Cloudera Manager Agent on the Hive Metastore Server host, check the status of the Cloudera Manager Agent by running /etc/init.d/cloudera-scm-agent status on the Hive Metastore Server host, or look in the Cloudera Manager Agent logs on the Hive Metastore Server host for more details. This test can be enabled or disabled using the Hive Metastore Server Process Health Test Hive Metastore Server monitoring setting.

Short Name: Process Status

This Hive Metastore Server health test checks the amount of swap memory in use by the role. A failure of this health test may indicate that your machine is overloaded. This test can be configured using the Process Swap Memory Thresholds monitoring settings.

Short Name: Swap Memory Usage

This Hive Metastore Server health test checks that the Hive Metastore Server has not recently exited unexpectedly. The test returns "Bad" health if the number of unexpected exits exceeds a critical threshold. For example, if this test is configured with a critical threshold of 1, this test returns "Good" health if there have been no unexpected exits recently. If 1 or more unexpected exits occured recently, this test returns "Bad" health. The test also indicates whether any of the exits were caused by an OutOfMemory error if the Cloudera Manager Kill When Out of Memory monitoring setting is enabled. This test can be configured using the Unexpected Exits Thresholds and Unexpected Exits Monitoring Period Hive Metastore Server monitoring settings.

Short Name: Unexpected Exits