JournalNode Health Tests

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

Short Name: Audit Pipeline Test

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

Short Name: File Descriptors

This is a JournalNode health test that checks the JournalNode's fsync latency. This test returns "Bad" health if the 99th percentile fsync latency over the previous minute is above a configured threshold value. Poor fsync performance may indicate a bad or overloaded disk and will negatively impact the performance of HDFS metadata operations performed by the NameNode. This test can be configured using the JournalNode Fsync Latency Thresholds JournalNode monitoring settings.

Short Name: Fsync Latency

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

Short Name: GC Duration

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

Short Name: Heap Dump Directory Free Space

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

Short Name: Host Health

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

Short Name: JournalNode Edits Directory Free Space

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

Short Name: Log Directory Free Space

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

Short Name: Process Status

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

This is a JournalNode health test that checks that the active NameNode is in sync with this JournalNode. This test returns "Bad" health if the active NameNode is out-of-sync with the JournalNode. This test is disabled when there is no active NameNode. This test can be configured using the Active NameNode Sync Status Health Check and Active NameNode Sync Status Startup Tolerance JournalNode monitoring settings.

Short Name: Sync Status

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

Short Name: Web Server Status