JournalNode Health Tests

JournalNode Audit Pipeline Test

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

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

JournalNode File Descriptors

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

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
journalnode_fd_thresholds
Default Value
critical:70.0, warning:50.0
Unit(s)
PERCENT

JournalNode Fsync Latency

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

JournalNode Fsync Latency Thresholds

Description
The health test thresholds for JournalNode fsync latency.
Template Name
journalnode_fsync_latency_thresholds
Default Value
critical:3000.0, warning:1000.0
Unit(s)
MILLISECONDS

JournalNode GC Duration

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

Garbage Collection Duration Monitoring Period

Description
The period to review when computing the moving average of garbage collection time.
Template Name
journalnode_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
journalnode_gc_duration_thresholds
Default Value
critical:60.0, warning:30.0
Unit(s)
no unit

JournalNode Heap Dump Directory Free Space

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

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

JournalNode Host Health

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

JournalNode Host Health Test

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

JournalNode JournalNode Edits Directory Free Space

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

JournalNode Edits Directory Free Space Monitoring Absolute Thresholds

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

JournalNode Edits Directory Free Space Monitoring Percentage Thresholds

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

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

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

JournalNode Process Status

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

JournalNode Process Health Test

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

JournalNode Swap Memory Usage

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

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

JournalNode Sync Status

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

Active NameNode Sync Status Health Check

Description
Enables the health check that verifies the active NameNode's sync status to the JournalNode
Template Name
journalnode_sync_status_enabled
Default Value
true
Unit(s)
no unit

Active NameNode Sync Status Startup Tolerance

Description
The amount of time at JournalNode startup allowed for the active NameNode to get in sync with the JournalNode.
Template Name
journalnode_sync_status_startup_tolerance
Default Value
180
Unit(s)
SECONDS

JournalNode Unexpected Exits

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

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

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

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
journalnode_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
journalnode_web_metric_collection_thresholds
Default Value
critical:never, warning:10000.0
Unit(s)
MILLISECONDS