Impala Llama ApplicationMaster Health Tests

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

Short Name: File Descriptors

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

Short Name: Heap Dump Directory Free Space

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

Short Name: Host Health

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

Short Name: Log Directory Free Space

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

Short Name: Process Status

This Impala Llama ApplicationMaster 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 Impala Llama ApplicationMaster health test checks that the Impala Llama ApplicationMaster has not recently exited unexpectedly. The test returns "Bad" health if the number of unexpected exits goes above a critical threshold. For example, if this test is configured with a critical threshold of 1, this test would return "Good" health if there have been no unexpected exits recently. If there has been 1 or more unexpected exits recently, this test would return "Bad" health. This test can be configured using the Unexpected Exits Thresholds and Unexpected Exits Monitoring Period Impala Llama ApplicationMaster monitoring settings.

Short Name: Unexpected Exits