This Oozie Server health test checks that the Auditing for the Oozie 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 Oozie Server process. This test can fail either because the Cloudera Audit Server is not accepting audits, or the Cloudera Manager Agent on the Oozie 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 Oozie Server monitoring setting.

Short Name: Audit Pipeline Test

This is an Oozie Server health test that checks that a moving average of the size of the Oozie Server's callable queue does not exceed some percentage of the configured maximum size for the queue. The callable queue contains tasks (e.g., StartCommand task, ActionCommand task) for asynchronous execution. When the queue is full the callable queue service stops queuing tasks. This may cause running jobs and submissions of new jobs to fail. A failure of this health test indicates a high load on the Oozie Server. Make sure the Oozie server has enough heap and is not running out of memory. You can also increase the number of threads handling the callable queue items by changing Number Threads For Executing Callables and the max size of the callable queue by changing Maximum Callable Queue Size. This test can be configured using the Oozie Server Callable Queue Monitoring Threshold and Oozie Server Callable Queue Monitoring Period Oozie Server monitoring settings.

Short Name: Callable Queue Size

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

Short Name: File Descriptors

This Oozie Server health test checks that the filesystem containing the heap dump directory of this Oozie Server 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 Oozie Server monitoring settings.

Short Name: Heap Dump Directory Free Space

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

Short Name: Host Health

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

Short Name: Log Directory Free Space

This is an Oozie Server health test that verifies that the installed shared library is correct. If the shared library is missing, is out-of-sync with the Oozie build version, or does not match the Oozie MapReduce service dependency, the check will return "Bad" health. Follow the instructions in the Cloudera Manager documentation to install or upgrade it. For other failures of this health test, consult the Cloudera Manager Service Monitor logs. This test can be enabled or disabled using the Enable Oozie Server Shared Libraries Version Check Oozie Server monitoring setting.

Short Name: Oozie Server Shared Library Check

This Oozie Server health test checks that the Oozie Server threads are not experiencing long scheduling pauses. The test uses a pause monitoring thread in the Oozie Server that tracks scheduling delay by noting if it is run on its requested schedule. If the thread is not run on its requested schedule, the delay is noted and considered pause time. The health test checks that no more than some percentage of recent time is spent paused. A failure of this health test may indicate that the Oozie Server is not getting enough CPU resources, or that it is spending too much time doing garbage collection. Inspect the Oozie Server logs for any pause monitor output and check garbage collection metrics exposed by the Oozie Server. This test can be configured using the Pause Duration Thresholds and Pause Duration Monitoring Period Oozie Server monitoring settings.

Short Name: Pause Duration

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

Short Name: Process Status

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

Short Name: Unexpected Exits

This health test checks that the role's web server is responding quickly to requests by the Cloudera Manager Service Monitor, and that the Cloudera Manager Service Monitor can collect metrics from the web server. Failure of this health test may indicate a problem with the web server of the Oozie Server, a misconfiguration of the Oozie Server, or a problem with the Cloudera Manager Service Monitor. Consult the Cloudera Manager Service Monitor logs and the logs of the Oozie Server for more detail. If the test failure message indicates a communication problem, the Cloudera Manager Service Monitor's HTTP requests to the Oozie Server's web server are failing or timing out. If the test's failure message indicates an unexpected response, the Oozie Server's web server responded to the Cloudera Manager Service Monitor's request, but the response could not be interpreted for some reason. This test can be configured using the Web Metric Collection Oozie Server monitoring setting.

Short Name: Web Server Status