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

Short Name: File Descriptors

This Load Balancer health test checks that the filesystem containing the heap dump directory of this Load Balancer has sufficient free space. This test can be configured using the Heap Dump Directory Free Space Monitoring Absolute Thresholds and Heap Dump Directory Free Space Monitoring Percentage Thresholds Load Balancer monitoring settings.

Short Name: Heap Dump Directory Free Space

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

Short Name: Host Health

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

Short Name: Log Directory Free Space

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

Short Name: Process Status

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

Short Name: Unexpected Exits