SecondaryNameNode Health Tests

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

Short Name: Audit Pipeline Test

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

Short Name: File Descriptors

This SecondaryNameNode health test checks that the SecondaryNameNode 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 SecondaryNameNode. This test can be configured using the Garbage Collection Duration Thresholds and Garbage Collection Duration Monitoring Period SecondaryNameNode monitoring settings.

Short Name: GC Duration

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

Short Name: HDFS Checkpoint Directories Free Space

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

Short Name: Heap Dump Directory Free Space

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

Short Name: Host Health

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

Short Name: Log Directory Free Space

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

Short Name: Process Status

This SecondaryNameNode 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 SecondaryNameNode health test checks that the SecondaryNameNode 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 SecondaryNameNode 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 SecondaryNameNode, a misconfiguration of the SecondaryNameNode, or a problem with the Cloudera Manager Agent. Consult the Cloudera Manager Agent logs and the logs of the SecondaryNameNode for more detail. If the test failure message indicates a communication problem, the Cloudera Manager Agent's HTTP requests to the SecondaryNameNode's web server are failing or timing out. If the test's failure message indicates an unexpected response, the SecondaryNameNode'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 SecondaryNameNode monitoring setting.

Short Name: Web Server Status