Garbage Collector Health Tests

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

Short Name: Audit Pipeline Test

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

Short Name: File Descriptors

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

Short Name: Host Health

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

Short Name: Process Status

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

Short Name: Unexpected Exits