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

Short Name: Audit Pipeline Test

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

Short Name: File Descriptors

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

Short Name: Host Health

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

Short Name: Process Status

This Navigator HSM KMS Metastore 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 Navigator HSM KMS Metastore health test checks that the Navigator HSM KMS Metastore 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 Navigator HSM KMS Metastore monitoring settings.

Short Name: Unexpected Exits