JobHistory Server Health Tests

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

Short Name: File Descriptors

This JobHistory Server health test checks that the JobHistory Server is not spending too much time performing Java garbage collection. It checks that no more than some percentage of recent time is spent performing Java garbage collection. A failure of this health test may indicate a capacity planning problem or misconfiguration of the JobHistory Server. This test can be configured using the Garbage Collection Duration Thresholds and Garbage Collection Duration Monitoring Period JobHistory Server monitoring settings.

Short Name: GC Duration

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

Short Name: Host Health

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

Short Name: Log Directory Free Space

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

Short Name: Process Status

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

Short Name: Web Server Status