Worker Health Tests

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

Short Name: File Descriptors

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

Short Name: Host Health

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

Short Name: Process Status

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

Short Name: Unexpected Exits