Impala StateStore Health Tests

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

Short Name: File Descriptors

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

Short Name: Heap Dump Directory Free Space

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

Short Name: Host Health

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

Short Name: Log Directory Free Space

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

Short Name: Process Status

This Impala StateStore health test checks that the size of the resident set does not rise above a configured threshold value. A failure of this health test may indicates that the Impala StateStore process is consuming more memory than expected. It is possible that that unexpected memory consumption may lead to swapping and decreased performance for processes running on the same host as this Impala StateStore. Increased Impala StateStore memory consumption may be caused by an increased workload on the Impala service, or by a bug in the Impala StateStore software. To avoid failures of this health test, free up additional memory for this Impala StateStore process and increase the Resident Set Size Thresholds monitoring setting. This test can be configured using the Resident Set Size Thresholds Impala StateStore monitoring setting.

Short Name: Resident Set Size

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

Short Name: Unexpected Exits

This health test checks that the role's web server is responding quickly to requests by the Cloudera Manager Agent, and that the Cloudera Manager Agent can collect metrics from the web server. Failure of this health test may indicate a problem with the web server of the Impala StateStore, a misconfiguration of the Impala StateStore, or a problem with the Cloudera Manager Agent. Consult the Cloudera Manager Agent logs and the logs of the Impala StateStore for more detail. If the test failure message indicates a communication problem, the Cloudera Manager Agent's HTTP requests to the Impala StateStore's web server are failing or timing out. If the test's failure message indicates an unexpected response, the Impala StateStore's web server responded to the Cloudera Manager Agent's request, but the response could not be interpreted for some reason. This test can be configured using the Web Metric Collection Impala StateStore monitoring setting.

Short Name: Web Server Status