DataNode Health Tests

DataNode Audit Pipeline Test

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

DataNode Block Count

This is a DataNode health test that checks for whether the DataNode has too many blocks. Having too many blocks on a DataNode may affect the DataNode's performance. A DataNode with a large number of blocks will require a larger java heap and may experience longer garbage collection pauses. Additionally, a large number of blocks may be an indicator of the presence of many small files. HDFS is not optimized for dealing with many small files, and processing times may suffer when operating across many small files. If only some DataNodes have a high number of blocks, running the HDFS Rebalance command may address this issue by moving data between DataNodes. If the HDFS Rebalance command reports the cluster as balanced without fixing the block imbalance then the problem is related to the presence of many small files. Consult the HDFS documentation for best-practices on addressing this issue. If many small files is not a concern for your use case, consider disabling this health test. If all DataNodes have a high number of blocks and the issue is not related to small files, additional DataNodes should be added. This test can be configured using the DataNode Block Count Thresholds DataNode monitoring setting.

Short Name: Block Count

DataNode Block Count Thresholds

Description
The health test thresholds of the number of blocks on a DataNode
Template Name
datanode_block_count_thresholds
Default Value
CDH=[[CDH 4.0.0..CDH 4.5.0)=critical:never, warning:200000.0, [CDH 4.5.0..CDH 6.0.0)=critical:never, warning:500000.0, [CDH 6.0.0..CDH 8.0.0)=critical:never, warning:1000000.0]
Unit(s)
no unit

DataNode Data Directory Status

This is a DataNode health test that checks for whether the DataNode has reported any failed volumes. A failure of this health test indicates that there is a problem with one or more volumes on the DataNode. See the DataNode system for more information. This test can be configured using the DataNode Volume Failures Thresholds DataNode monitoring setting.

Short Name: Data Directory Status

DataNode Volume Failures Thresholds

Description
The health test thresholds of failed volumes in a DataNode.
Template Name
datanode_volume_failures_thresholds
Default Value
critical:any, warning:never
Unit(s)
no unit

DataNode DataNode Data Directory Free Space

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

Short Name: DataNode Data Directory Free Space

DataNode Data Directory Free Space Monitoring Absolute Thresholds

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

DataNode Data Directory Free Space Monitoring Percentage Thresholds

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

DataNode File Descriptors

This DataNode health test checks that the number of file descriptors used does not rise above some percentage of the DataNode 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 DataNode 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
datanode_fd_thresholds
Default Value
critical:70.0, warning:50.0
Unit(s)
PERCENT

DataNode Free Space

This is a DataNode health test that checks that the amount of free space available for HDFS block data on the DataNode does not fall below some percentage of total configured capacity of the DataNode. A failure of this health test may indicate a capacity planning problem. Try adding more disk capacity and additional data directories to the DataNode, or add additional DataNodes and take steps to rebalance your HDFS cluster. This test can be configured using the DataNode Free Space Monitoring Thresholds DataNode monitoring setting.

Short Name: Free Space

DataNode Free Space Monitoring Thresholds

Description
The health test thresholds of free space in a DataNode. Specified as a percentage of the capacity on the DataNode.
Template Name
datanode_free_space_thresholds
Default Value
critical:10.0, warning:20.0
Unit(s)
PERCENT

DataNode Heap Dump Directory Free Space

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

DataNode Host Health

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

Short Name: Host Health

DataNode Host Health Test

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

DataNode Log Directory Free Space

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

DataNode NameNode Connectivity

This is a DataNode health test that checks that all the running NameNodes in the HDFS service consider the DataNode alive. A failure of this health test may indicate that the DataNode is having trouble communicating with some or all NameNodes in the service. Look in the DataNode logs for more details. This test can be enabled or disabled using the DataNode Connectivity Health Test DataNode monitoring setting. The DataNode Connectivity Tolerance at Startup DataNode monitoring setting and the Health Test Startup Tolerance NameNode monitoring setting can be used to control the test's tolerance windows around DataNode and NameNode restarts respectively.

Short Name: NameNode Connectivity

DataNode Connectivity Health Test

Description
Enables the health test that verifies the DataNode is connected to the NameNode
Template Name
datanode_connectivity_health_enabled
Default Value
true
Unit(s)
no unit

DataNode Connectivity Tolerance at Startup

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

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
namenode_startup_tolerance
Default Value
5
Unit(s)
MINUTES

DataNode Pause Duration

This DataNode health test checks that the DataNode threads are not experiencing long scheduling pauses. The test uses a pause monitoring thread in the DataNode 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 DataNode is not getting enough CPU resources, or that it is spending too much time doing garbage collection. Inspect the DataNode logs for any pause monitor output and check garbage collection metrics exposed by the DataNode. This test can be configured using the Pause Duration Thresholds and Pause Duration Monitoring Period DataNode monitoring settings.

Short Name: Pause Duration

Pause Duration Monitoring Period

Description
The period to review when computing the moving average of extra time the pause monitor spent paused.
Template Name
datanode_pause_duration_window
Default Value
5
Unit(s)
MINUTES

Pause Duration Thresholds

Description
The health test thresholds for the weighted average extra time the pause monitor spent paused. Specified as a percentage of elapsed wall clock time.
Template Name
datanode_pause_duration_thresholds
Default Value
critical:60.0, warning:30.0
Unit(s)
no unit

DataNode Process Status

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

Short Name: Process Status

DataNode Process Health Test

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

DataNode Swap Memory Usage

This DataNode 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

DataNode Swap Memory Usage Rate Beta

This DataNode 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

DataNode Transceiver Usage

This is a DataNode health test that checks for whether the DataNode transceivers usage is nearing the configured transceivers limit. A transceiver is a thread used to transfer data into or out of the DataNode. If a DataNode hits its transceivers limit, HDFS reads and writes begin to fail. This test can be configured using the DataNode Transceivers Usage Thresholds DataNode monitoring setting. The Maximum Number of Transfer Threads DataNode setting controls the DataNode transceivers limit.

Short Name: Transceiver Usage

DataNode Transceivers Usage Thresholds

Description
The health test thresholds of transceivers usage in a DataNode. Specified as a percentage of the total configured number of transceivers.
Template Name
datanode_transceivers_usage_thresholds
Default Value
critical:95.0, warning:75.0
Unit(s)
PERCENT

Maximum Number of Transfer Threads

Description
Specifies the maximum number of threads to use for transferring data in and out of the DataNode.
Template Name
dfs_datanode_max_xcievers
Default Value
4096
Unit(s)
no unit

DataNode Unexpected Exits

This DataNode health test checks that the DataNode 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 DataNode 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

DataNode 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 DataNode, a misconfiguration of the DataNode, or a problem with the Cloudera Manager Agent. Consult the Cloudera Manager Agent logs and the logs of the DataNode for more detail. If the test failure message indicates a communication problem, the Cloudera Manager Agent's HTTP requests to the DataNode's web server are failing or timing out. If the test's failure message indicates an unexpected response, the DataNode'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 DataNode 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
datanode_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
datanode_web_metric_collection_thresholds
Default Value
critical:never, warning:10000.0
Unit(s)
MILLISECONDS