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

Short Name: File Descriptors

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

Short Name: Host Health

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

Short Name: Process Status

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

Short Name: Unexpected Exits