HiveServer2 Health Tests

This HiveServer2 health test checks that the Auditing for the HiveServer2 role is getting processed correctly and is not blocked. A failure of this health test may indicate a problem with the audit pipeline of HiveServer2 process. This test can fail either because the Cloudera Audit Server is not accepting audits, or the Cloudera Manager Agent on the HiveServer2 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 HiveServer2 monitoring setting.

Short Name: Audit Pipeline Test

This HiveServer2 health test checks that the number of file descriptors used does not rise above some percentage of the HiveServer2 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 HiveServer2 monitoring setting.

Short Name: File Descriptors

This HiveServer2 health test checks that the filesystem containing the heap dump directory of this HiveServer2 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 HiveServer2 monitoring settings.

Short Name: Heap Dump Directory Free Space

This is a HiveServer2 health test that checks that the filesystem containing the Hive Downloaded Resources Directory of this HiveServer2 has sufficient free space. See the Hive Downloaded Resources Directory description on the HiveServer2 configuration page for more information on this directory type. This test can be configured using the Hive Downloaded Resources Directory Free Space Monitoring Absolute Thresholds and Hive Downloaded Resources Directory Free Space Monitoring Percentage Thresholds HiveServer2 monitoring settings.

Short Name: Hive Downloaded Resources Directory Free Space

This is a HiveServer2 health test that checks that the filesystem containing the Hive Local Scratch Directory of this HiveServer2 has sufficient free space. See the Hive Local Scratch Directory description on the HiveServer2 configuration page for more information on this directory type. This test can be configured using the Hive Local Scratch Directory Free Space Monitoring Absolute Thresholds and Hive Local Scratch Directory Free Space Monitoring Percentage Thresholds HiveServer2 monitoring settings.

Short Name: Hive Local Scratch Directory Free Space

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

Short Name: Host Health

This HiveServer2 health test checks that the filesystem containing the log directory of this HiveServer2 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 HiveServer2 monitoring settings.

Short Name: Log Directory Free Space

This HiveServer2 health test checks that the HiveServer2 threads are not experiencing long scheduling pauses. The test uses a pause monitoring thread in the HiveServer2 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 HiveServer2 is not getting enough CPU resources, or that it is spending too much time doing garbage collection. Inspect the HiveServer2 logs for any pause monitor output and check garbage collection metrics exposed by the HiveServer2. This test can be configured using the Pause Duration Thresholds and Pause Duration Monitoring Period HiveServer2 monitoring settings.

Short Name: Pause Duration

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

Short Name: Process Status

This HiveServer2 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 HiveServer2 health test checks that the HiveServer2 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 HiveServer2 monitoring settings.

Short Name: Unexpected Exits