History Server Health Tests

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

Short Name: Audit Pipeline Test

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

Short Name: File Descriptors

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

Short Name: Host Health

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

Short Name: Process Status

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

Short Name: Unexpected Exits