Impala Catalog Server Health Tests

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

Short Name: File Descriptors

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

Short Name: Host Health

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

Short Name: Log Directory Free Space

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

Short Name: Process Status

This Impala Catalog Server 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 Catalog Server 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 Catalog Server. Increased Impala Catalog Server memory consumption may be caused by an increased workload on the Impala service, or by a bug in the Impala Catalog Server software. To avoid failures of this health test, free up additional memory for this Impala Catalog Server process and increase the Resident Set Size Thresholds monitoring setting. This test can be configured using the Resident Set Size Thresholds Impala Catalog Server monitoring setting.

Short Name: Resident Set Size

This is a Catalog Server health test that checks whether the StateStore considers the Catalog Server alive. A failure of this health test may indicate that the Catalog Server is having trouble communicating with the StateStore. Look in the Catalog Server logs for more details. This test may return an unknown result if the Service Monitor is not able to communicate with the StateStore web server. Check the status of the StateStore web server and the Service Monitor logs if this test is returning an unknown result. This test can be enabled or disabled using the Catalog Server Connectivity Health Test Catalog Server monitoring setting. The Catalog Server Connectivity Tolerance at Startup Catalog Server monitoring setting and the Health Check Startup Tolerance StateStore monitoring setting can be used to control the test's tolerance windows around Catalog Server and StateStore restarts respectively.

Short Name: StateStore Connectivity

This Impala Catalog Server health test checks that the Impala Catalog Server 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 Catalog Server 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 Catalog Server, a misconfiguration of the Impala Catalog Server or a problem with the Cloudera Manager Agent. Consult the Cloudera Manager Agent logs and the logs of the Impala Catalog Server for more detail. If the test's failure message indicates a communication problem, the Cloudera Manager Agent's HTTP requests to the Impala Catalog Server's web server are failing or timing out. If the test's failure message indicates an unexpected response, the Impala Catalog Server'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 Catalog Server monitoring setting.

Short Name: Web Server Status