NodeManager Health Tests

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

Short Name: Audit Pipeline Test

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

Short Name: File Descriptors

This NodeManager health test checks that the NodeManager is not spending too much time performing Java garbage collection. It checks that no more than some percentage of recent time is spent performing Java garbage collection. A failure of this health test may indicate a capacity planning problem or misconfiguration of the NodeManager. This test can be configured using the Garbage Collection Duration Thresholds and Garbage Collection Duration Monitoring Period NodeManager monitoring settings.

Short Name: GC Duration

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

Short Name: Heap Dump Directory Free Space

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

Short Name: Host Health

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

Short Name: Log Directory Free Space

This is a NodeManager health test that checks that the filesystem containing the NodeManager Container Log Directories of this NodeManager has sufficient free space. See the NodeManager Container Log Directories description on the NodeManager configuration page for more information on this directory type. This test can be configured using the NodeManager Container Log Directories Free Space Monitoring Absolute Thresholds and NodeManager Container Log Directories Free Space Monitoring Percentage Thresholds NodeManager monitoring settings.

Short Name: NodeManager Container Log Directories Free Space

This is a NodeManager health test that checks whether the ResourceManager considers the NodeManager healthly. A failure of this health test indicates that the NodeManager disk health checker or a health check script, if one is configured, reported an unhealthy condition. The NodeManager health report may include more details about the failure. Look in the NodeManager logs for more details. This test may return an unknown result if the Service Monitor is not able to communicate with the ResourceManager web server. Check the status of the ResourceManager web server and the Service Monitor logs if this test is returning an unknown result. This test can be enabled or disabled using the NodeManager Health Checker Health Check NodeManager monitoring setting. The NodeManager Connectivity Tolerance at Startup Node Manager monitoring setting and the Health Test Startup Tolerance ResourceManager monitor setting can be used to control the test's tolerance windows around NodeManager and ResourceManager restarts, respectively. The NodeManager disk health checker configuration can be configured using Disk Health Checker Minimum Health Disks Fraction, Disk Health Checker Minimum Health Disk Space, and Dish Health Checker Max Disk Utilization Percent.

Short Name: NodeManager Health Checker

This is a NodeManager health test that checks that the filesystem containing the NodeManager Local Directories of this NodeManager has sufficient free space. See the NodeManager Local Directories description on the NodeManager configuration page for more information on this directory type. This test can be configured using the NodeManager Local Directories Free Space Monitoring Absolute Thresholds and NodeManager Local Directories Free Space Monitoring Percentage Thresholds NodeManager monitoring settings.

Short Name: NodeManager Local Directories Free Space

This is a NodeManager health test that checks that the filesystem containing the NodeManager Recovery Directory of this NodeManager has sufficient free space. See the NodeManager Recovery Directory description on the NodeManager configuration page for more information on this directory type. This test can be configured using the NodeManager Recovery Directory Free Space Monitoring Absolute Thresholds and NodeManager Recovery Directory Free Space Monitoring Percentage Thresholds NodeManager monitoring settings.

Short Name: NodeManager Recovery Directory Free Space

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

Short Name: Process Status

This is a NodeManager health test that checks whether the ResourceManager considers the NodeManager alive. A failure of this health test may indicate that the NodeManager is having trouble communicating with the ResourceManager. Look in the NodeManager logs for more details. This test may return an unknown result if the Service Monitor is not able to communicate with the ResourceManager web server. Check the status of the ResourceManager web server and the Service Monitor logs if this test is returning an unknown result. This test can be enabled or disabled using the NodeManager Connectivity Health Check NodeManager monitoring setting. The NodeManager Connectivity Tolerance at Startup NodeManager monitoring setting and the Health Test Startup Tolerance ResourceManager monitoring setting can be used to control the test's tolerance windows around NodeManager and ResourceManager restarts respectively.

Short Name: ResourceManager Connectivity

This NodeManager 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 NodeManager health test checks that the NodeManager 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 NodeManager 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 Agent, and that the Cloudera Manager Agent can collect metrics from the web server. Failure of this health test may indicate a problem with the web server of the NodeManager, a misconfiguration of the NodeManager, or a problem with the Cloudera Manager Agent. Consult the Cloudera Manager Agent logs and the logs of the NodeManager for more detail. If the test failure message indicates a communication problem, the Cloudera Manager Agent's HTTP requests to the NodeManager's web server are failing or timing out. If the test's failure message indicates an unexpected response, the NodeManager's web server responded to the Cloudera Manager Agent's request, but the response could not be interpreted for some reason. This test can be configured using the Web Metric Collection NodeManager monitoring setting.

Short Name: Web Server Status