Kafka MirrorMaker Health Tests
Kafka MirrorMaker File Descriptors
This Kafka MirrorMaker health test checks that the number of file descriptors used does not rise above some percentage of the Kafka MirrorMaker 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 Kafka MirrorMaker monitoring setting.
Short Name: File Descriptors
Property Name | Description | Template Name | Default Value | Unit |
---|---|---|---|---|
File Descriptor Monitoring Thresholds | The health test thresholds of the number of file descriptors used. Specified as a percentage of file descriptor limit. | kafka_mirror_maker_fd_thresholds | critical:70.0, warning:50.0 | PERCENT |
Kafka MirrorMaker Host Health
This Kafka MirrorMaker health test factors in the health of the host upon which the Kafka MirrorMaker is running. A failure of this test means that the host running the Kafka MirrorMaker is experiencing some problem. See that host's status page for more details.This test can be enabled or disabled using the Kafka MirrorMaker Host Health Test Kafka MirrorMaker monitoring setting.
Short Name: Host Health
Property Name | Description | Template Name | Default Value | Unit |
---|---|---|---|---|
Kafka MirrorMaker Host Health Test | When computing the overall Kafka MirrorMaker health, consider the host's health. | kafka_mirror_maker_host_health_enabled | true | no unit |
Kafka MirrorMaker Process Status
This Kafka MirrorMaker health test checks that the Cloudera Manager Agent on the Kafka MirrorMaker host is heart beating correctly and that the process associated with the Kafka MirrorMaker role is in the state expected by Cloudera Manager. A failure of this health test may indicate a problem with the Kafka MirrorMaker process, a lack of connectivity to the Cloudera Manager Agent on the Kafka MirrorMaker host, or a problem with the Cloudera Manager Agent. This test can fail either because the Kafka MirrorMaker has crashed or because the Kafka MirrorMaker will not start or stop in a timely fashion. Check the Kafka MirrorMaker logs for more details. If the test fails because of problems communicating with the Cloudera Manager Agent on the Kafka MirrorMaker host, check the status of the Cloudera Manager Agent by running /etc/init.d/cloudera-scm-agent status on the Kafka MirrorMaker host, or look in the Cloudera Manager Agent logs on the Kafka MirrorMaker host for more details. This test can be enabled or disabled using the Kafka MirrorMaker Process Health Test Kafka MirrorMaker monitoring setting.
Short Name: Process Status
Property Name | Description | Template Name | Default Value | Unit |
---|---|---|---|---|
Kafka MirrorMaker Process Health Test | Enables the health test that the Kafka MirrorMaker's process state is consistent with the role configuration | kafka_mirror_maker_scm_health_enabled | true | no unit |
Kafka MirrorMaker Swap Memory Usage
This Kafka MirrorMaker 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
Property Name | Description | Template Name | Default Value | Unit |
---|---|---|---|---|
Process Swap Memory Thresholds | The health test thresholds on the swap memory usage of the process. | process_swap_memory_thresholds | critical:never, warning:any | BYTES |
Kafka MirrorMaker Unexpected Exits
This Kafka MirrorMaker health test checks that the Kafka MirrorMaker 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 Kafka MirrorMaker 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 test 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 |