SRM Service Health Tests

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

Short Name: Audit Pipeline Test

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

Short Name: File Descriptors

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

Short Name: Host Health

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

Short Name: Log Directory Free Space

Short Name: Metrics Processor Health Test

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

Short Name: Process Status

Short Name: SRM Service - Remote SRM Service Discovery Endpoint Groups Aggregated Health Test

Short Name: SRM Service - Remote SRM Service Discovery Endpoint Groups Validated With Health Checks Aggregated Health Test

Short Name: SRM Service - Remote SRM Service Discovery Topic Consumers Aggregated Health Test

Short Name: SRM Service - Service Discovery Heartbeat Producers Aggregated Health Test

Short Name: SRM Status Processor Streams App Kafka Connection Health Test

Short Name: SRM Streams App Kafka Connection Health Test

Short Name: Status Metrics Processor Health Test

This SRM Service 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 SRM Service 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 SRM Service health test checks that the SRM Service 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 SRM Service monitoring settings.

Short Name: Unexpected Exits