SecondaryNameNode Health Checks
SecondaryNameNode Checkpoint Directories Free Space
This is a Secondary NameNode health check that checks that the filesystems containing the checkpoint directories have sufficient free space. This test can be configured using the Checkpoint Directories Free Space Monitoring Absolute Thresholds and Checkpoint Directories Free Space Monitoring Percentage Thresholds Secondary NameNode monitoring settings.
Short Name: Checkpoint Directories Free Space
Property Name | Description | Template Name | Default Value | Unit |
---|---|---|---|---|
Checkpoint Directories Free Space Monitoring Absolute Thresholds | The health check thresholds for monitoring of free space on the filesystems that contain this role's checkpoint directories. | secondarynamenode_checkpoint_directories_free_space_absolute_thresholds | critical:5368709120.000000, warning:10737418240.000000 | BYTES |
Checkpoint Directories Free Space Monitoring Percentage Thresholds | The health check thresholds for monitoring of free space on the filesystems that contain this role's checkpoint directories. Specified as a percentage of the capacity on the filesystem. This setting is not used if a Checkpoint Directories Free Space Monitoring Absolute Thresholds setting is configured. | secondarynamenode_checkpoint_directories_free_space_percentage_thresholds | critical:never, warning:never | PERCENT |
SecondaryNameNode File Descriptors
This SecondaryNameNode health check 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 check 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
Property Name | Description | Template Name | Default Value | Unit |
---|---|---|---|---|
File Descriptor Monitoring Thresholds | The health check thresholds of the number of file descriptors used. Specified as a percentage of file descriptor limit. | secondarynamenode_fd_thresholds | critical:70.000000, warning:50.000000 | PERCENT |
SecondaryNameNode GC Duration
This SecondaryNameNode health check 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 check may indicate a capacity planning problem or misconfiguration of the SecondaryNameNode. This test can be configured using the Secondary NameNode Garbage Collection Duration Thresholds and Secondary NameNode Garbage Collection Duration Monitoring Period SecondaryNameNode monitoring settings.
Short Name: GC Duration
Property Name | Description | Template Name | Default Value | Unit |
---|---|---|---|---|
Secondary NameNode Garbage Collection Duration Monitoring Period | The period to review when computing the moving average of garbage collection time. | secondarynamenode_gc_duration_window | 5 | MINUTES |
Secondary NameNode Garbage Collection Duration Thresholds | The health check thresholds for the weighted average time spent in Java garbage collection. Specified as a percentage of elapsed wall clock time. See Secondary NameNode Garbage Collection Duration Monitoring Period. | secondarynamenode_gc_duration_thresholds | critical:60.000000, warning:30.000000 | PERCENT |
SecondaryNameNode Host Health
This SecondaryNameNode health check factors in the health of the host upon which the SecondaryNameNode is running. A failure of this check 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 Secondary NameNode Host Health Check SecondaryNameNode monitoring setting.
Short Name: Host Health
Property Name | Description | Template Name | Default Value | Unit |
---|---|---|---|---|
Secondary NameNode Host Health Check | When computing the overall Secondary NameNode health, consider the host's health. | secondarynamenode_host_health_enabled | true | no unit |
SecondaryNameNode Log Directory Free Space
This SecondaryNameNode health check 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
Property Name | Description | Template Name | Default Value | Unit |
---|---|---|---|---|
Log Directory Free Space Monitoring Absolute Thresholds | The health check thresholds for monitoring of free space on the filesystem that contains this role's log directory. | log_directory_free_space_absolute_thresholds | critical:5368709120.000000, warning:10737418240.000000 | BYTES |
Log Directory Free Space Monitoring Percentage Thresholds | The health check 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. | log_directory_free_space_percentage_thresholds | critical:never, warning:never | PERCENT |
SecondaryNameNode Process Status
This SecondaryNameNode health check 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 check 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 check 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 check 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 Secondary NameNode Process Health Check SecondaryNameNode monitoring setting.
Short Name: Process Status
Property Name | Description | Template Name | Default Value | Unit |
---|---|---|---|---|
Secondary NameNode Process Health Check | Enables the health check that the Secondary NameNode's process state is consistent with the role configuration | secondarynamenode_scm_health_enabled | true | no unit |
SecondaryNameNode Unexpected Exits
This SecondaryNameNode health check checks that the SecondaryNameNode has not recently exited unexpectedly. The check returns "Bad" health if the number of unexpected exits goes above a critical threshold. For example, if this check is configured with a critical threshold of 1, this check would return "Good" health if there have been no unexpected exits recently. If there has been 1 or more unexpected exits recently, this check would return "Bad" health. This test can be configured using the Unexpected Exits Thresholds and Unexpected Exits Monitoring Period SecondaryNameNode monitoring settings.
Short Name: Unexpected Exits
Property Name | Description | Template Name | Default Value | Unit |
---|---|---|---|---|
Unexpected Exits Monitoring Period | The period to review when computing unexpected exits. | unexpected_exits_window | 5 | MINUTES |
Unexpected Exits Thresholds | The health check thresholds for unexpected exits encountered within a recent period specified by the unexpected_exits_window configuration for the role. | unexpected_exits_thresholds | critical:any, warning:never | no unit |
SecondaryNameNode Web Server Status
This SecondaryNameNode health check checks that the web server of the SecondaryNameNode is responding quickly to requests by the Cloudera Manager agent, and that the Cloudera Manager agent can collect metrics from the web server. A failure of this health check 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's failure message indicates a communication problem, this means that the Cloudera Manager Agent's HTTP requests to the SecondaryNameNode's web server are failing or timing out. These requests are completely local to the SecondaryNameNode's host, and so should never fail under normal conditions. If the test's failure message indicates an unexpected response, then the SecondaryNameNode's web server responded to the Cloudera Manager Agent's request, but the Cloudera Manager Agent could not interpret the response for some reason. This test can be configured using the Web Metric Collection SecondaryNameNode monitoring setting.
Short Name: Web Server Status
Property Name | Description | Template Name | Default Value | Unit |
---|---|---|---|---|
Web Metric Collection | Enables the health check that the Cloudera Manager Agent can successfully contact and gather metrics from the web server. | secondarynamenode_web_metric_collection_enabled | true | no unit |
<< | ||
Terms and Conditions Privacy Policy |