NodeManager Health Tests

NodeManager Audit Pipeline Test

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

Monitoring Period For Audit Failures

Description: The period to review when checking if audits are blocked and not getting processed.
Template Name: mgmt_navigator_failure_window
Default Value: 20
Unit(s): MINUTES

Navigator Audit Failure Thresholds

Description: The health test thresholds for failures encountered when monitoring audits within a recent period specified by the mgmt_navigator_failure_window configuration for the role. The value that can be specified for this threshold is the number of bytes of audits data that is left to be sent to audit server.
Template Name: mgmt_navigator_failure_thresholds
Default Value: critical:any, warning:never
Unit(s): BYTES

Navigator Audit Pipeline Health Check

Description: Enable test of audit events processing pipeline. This will test if audit events are not getting processed by Audit Server for a role that generates audit.
Template Name: mgmt_navigator_status_check_enabled
Default Value: true
Unit(s): no unit

NodeManager File Descriptors

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

File Descriptor Monitoring Thresholds

Description: The health test thresholds of the number of file descriptors used. Specified as a percentage of file descriptor limit.
Template Name: nodemanager_fd_thresholds
Default Value: critical:70.0, warning:50.0
Unit(s): PERCENT

NodeManager GC Duration

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

Garbage Collection Duration Monitoring Period

Description: The period to review when computing the moving average of garbage collection time.
Template Name: nodemanager_gc_duration_window
Default Value: 5
Unit(s): MINUTES

Garbage Collection Duration Thresholds

Description: The health test thresholds for the weighted average time spent in Java garbage collection. Specified as a percentage of elapsed wall clock time.
Template Name: nodemanager_gc_duration_thresholds
Default Value: critical:60.0, warning:30.0
Unit(s): no unit

NodeManager Heap Dump Directory Free Space

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

Heap Dump Directory Free Space Monitoring Absolute Thresholds

Description: The health test thresholds for monitoring of free space on the filesystem that contains this role's heap dump directory.
Template Name: heap_dump_directory_free_space_absolute_thresholds
Default Value: critical:5.36870912E9, warning:1.073741824E10
Unit(s): BYTES

Heap Dump Directory Free Space Monitoring Percentage Thresholds

Description: The health test thresholds for monitoring of free space on the filesystem that contains this role's heap dump directory. Specified as a percentage of the capacity on that filesystem. This setting is not used if a Heap Dump Directory Free Space Monitoring Absolute Thresholds setting is configured.
Template Name: heap_dump_directory_free_space_percentage_thresholds
Default Value: critical:never, warning:never
Unit(s): PERCENT

NodeManager Host Health

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

NodeManager Host Health Test

Description: When computing the overall NodeManager health, consider the host's health.
Template Name: nodemanager_host_health_enabled
Default Value: true
Unit(s): no unit

NodeManager Log Directory Free Space

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

Log Directory Free Space Monitoring Absolute Thresholds

Description: The health test thresholds for monitoring of free space on the filesystem that contains this role's log directory.
Template Name: log_directory_free_space_absolute_thresholds
Default Value: critical:5.36870912E9, warning:1.073741824E10
Unit(s): BYTES

Log Directory Free Space Monitoring Percentage Thresholds

Description: The health test thresholds for monitoring of free space on the filesystem that contains this role's log directory. Specified as a percentage of the capacity on that filesystem. This setting is not used if a Log Directory Free Space Monitoring Absolute Thresholds setting is configured.
Template Name: log_directory_free_space_percentage_thresholds
Default Value: critical:never, warning:never
Unit(s): PERCENT

NodeManager NodeManager Container Log Directories 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

NodeManager Container Log Directories Free Space Monitoring Absolute Thresholds

Description: The health test thresholds for monitoring of free space on the filesystem that contains this role's NodeManager Container Log Directories.
Template Name: nodemanager_log_directories_free_space_absolute_thresholds
Default Value: critical:5.36870912E9, warning:1.073741824E10
Unit(s): BYTES

NodeManager Container Log Directories Free Space Monitoring Percentage Thresholds

Description: The health test thresholds for monitoring of free space on the filesystem that contains this role's NodeManager Container Log Directories. Specified as a percentage of the capacity on that filesystem. This setting is not used if a NodeManager Container Log Directories Free Space Monitoring Absolute Thresholds setting is configured.
Template Name: nodemanager_log_directories_free_space_percentage_thresholds
Default Value: critical:never, warning:never
Unit(s): PERCENT

NodeManager NodeManager Health Checker

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

Dish Health Checker Max Disk Utilization Percent

Description: The maximum percentage of disk space utilization allowed after which a disk is marked as bad. Values can range from 0.0 to 100.0. If the value is greater than or equal to 100, the NodeManager will check for full disk. This applies to local directories and log directories.
Template Name: yarn_nodemanager_disk_health_checker_max_disk_utilization_per_disk_percentage
Default Value: CDH=[[CDH 5.2.0..CDH 8.0.0)=90.0]
Unit(s): PERCENT

Disk Health Checker Minimum Health Disk Space

Description: The minimum space that must be available on a disk for it to be used. This applies to local directories and log directories.
Template Name: yarn_nodemanager_disk_health_checker_min_free_space_per_disk_mb
Default Value: CDH=[[CDH 5.2.0..CDH 8.0.0)=0]
Unit(s): MEGABYTES

Disk Health Checker Minimum Health Disks Fraction

Description: The minimum fraction of number of disks to be healthy for the NodeManager to launch new containers. This correspond to both local directories and log directories; that is, if there are fewer healthy local directories (or log directories) available, then new containers will not be launched on this node.
Template Name: yarn_nodemanager_disk_health_checker_min_healthy_disks
Default Value: 0.25
Unit(s): no unit

Health Test Startup Tolerance

Description: The amount of time allowed after this role is started that failures of health tests that rely on communication with this role will be tolerated.
Template Name: resourcemanager_startup_tolerance_minutes
Default Value: 5
Unit(s): MINUTES

NodeManager Connectivity Tolerance at Startup

Description: The amount of time to wait for the NodeManager to fully start up and connect to the ResourceManager before enforcing the connectivity check.
Template Name: nodemanager_connectivity_tolerance_seconds
Default Value: 180
Unit(s): SECONDS

NodeManager Health Checker Health Check

Description: Enables the health check that verifies the NodeManager is seen as healthy by the ResourceManager.
Template Name: nodemanager_health_checker_health_enabled
Default Value: true
Unit(s): no unit

NodeManager NodeManager Local Directories Free Space

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

NodeManager Local Directories Free Space Monitoring Absolute Thresholds

Description: The health test thresholds for monitoring of free space on the filesystem that contains this role's NodeManager Local Directories.
Template Name: nodemanager_local_data_directories_free_space_absolute_thresholds
Default Value: critical:5.36870912E9, warning:1.073741824E10
Unit(s): BYTES

NodeManager Local Directories Free Space Monitoring Percentage Thresholds

Description: The health test thresholds for monitoring of free space on the filesystem that contains this role's NodeManager Local Directories. Specified as a percentage of the capacity on that filesystem. This setting is not used if a NodeManager Local Directories Free Space Monitoring Absolute Thresholds setting is configured.
Template Name: nodemanager_local_data_directories_free_space_percentage_thresholds
Default Value: critical:never, warning:never
Unit(s): PERCENT

NodeManager NodeManager Recovery Directory 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

NodeManager Recovery Directory Free Space Monitoring Absolute Thresholds

Description: The health test thresholds for monitoring of free space on the filesystem that contains this role's NodeManager Recovery Directory.
Template Name: nodemanager_recovery_directory_free_space_absolute_thresholds
Default Value: critical:5.36870912E9, warning:1.073741824E10
Unit(s): BYTES

NodeManager Recovery Directory Free Space Monitoring Percentage Thresholds

Description: The health test thresholds for monitoring of free space on the filesystem that contains this role's NodeManager Recovery Directory. Specified as a percentage of the capacity on that filesystem. This setting is not used if a NodeManager Recovery Directory Free Space Monitoring Absolute Thresholds setting is configured.
Template Name: nodemanager_recovery_directory_free_space_percentage_thresholds
Default Value: critical:never, warning:never
Unit(s): PERCENT

NodeManager Process Status

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

NodeManager Process Health Test

Description: Enables the health test that the NodeManager's process state is consistent with the role configuration
Template Name: nodemanager_scm_health_enabled
Default Value: true
Unit(s): no unit

NodeManager ResourceManager Connectivity

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

Health Test Startup Tolerance

Description: The amount of time allowed after this role is started that failures of health tests that rely on communication with this role will be tolerated.
Template Name: resourcemanager_startup_tolerance_minutes
Default Value: 5
Unit(s): MINUTES

NodeManager Connectivity Health Check

Description: Enables the health check that verifies the NodeManager is connected to the ResourceManager.
Template Name: nodemanager_connectivity_health_enabled
Default Value: true
Unit(s): no unit

NodeManager Connectivity Tolerance at Startup

Description: The amount of time to wait for the NodeManager to fully start up and connect to the ResourceManager before enforcing the connectivity check.
Template Name: nodemanager_connectivity_tolerance_seconds
Default Value: 180
Unit(s): SECONDS

NodeManager Swap Memory Usage

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

Process Swap Memory Thresholds

Description: The health test thresholds on the swap memory usage of the process. This takes precedence over the host level threshold.
Template Name: process_swap_memory_thresholds
Default Value: critical:never, warning:200.0
Unit(s): BYTES

NodeManager Swap Memory Usage Rate Beta

This NodeManager health test checks the change of the amount of swap memory usage by the role during a predefined period. A failure of this health test may indicate that your machine is overloaded. This test can be configured using the Swap Memory Usage Rate Thresholds and Swap Memory Usage Rate Window monitoring settings.

Short Name: Swap Memory Usage Rate Beta

Swap Memory Usage Rate Thresholds

Description: The health test thresholds on the swap memory usage rate of the process. Specified as the change of the used swap memory during the predefined period.
Template Name: process_swap_memory_rate_thresholds
Default Value: critical:never, warning:never
Unit(s): BYTES

Swap Memory Usage Rate Window

Description: The period to review when computing unexpected swap memory usage change of the process.
Template Name: process_swap_memory_rate_window
Default Value: 5
Unit(s): MINUTES

NodeManager Unexpected Exits

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

Unexpected Exits Monitoring Period

Description: The period to review when computing unexpected exits.
Template Name: unexpected_exits_window
Default Value: 5
Unit(s): MINUTES

Unexpected Exits Thresholds

Description: The health test thresholds for unexpected exits encountered within a recent period specified by the unexpected_exits_window configuration for the role.
Template Name: unexpected_exits_thresholds
Default Value: critical:any, warning:never
Unit(s): no unit

NodeManager Web Server Status

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

Web Metric Collection

Description: Enables the health test that the Cloudera Manager Agent can successfully contact and gather metrics from the web server.
Template Name: nodemanager_web_metric_collection_enabled
Default Value: true
Unit(s): no unit

Web Metric Collection Duration

Description: The health test thresholds on the duration of the metrics request to the web server.
Template Name: nodemanager_web_metric_collection_thresholds
Default Value: critical:never, warning:10000.0
Unit(s): MILLISECONDS