Navigator Metadata Server Health Tests

This is a Navigator Metadata Server health test that checks that the filesystem containing the Audit Log Directory of this Navigator Metadata Server has sufficient free space. See the Audit Log Directory description on the Navigator Metadata Server configuration page for more information on this directory type. This test can be configured using the Audit Log Directory Free Space Monitoring Absolute Thresholds and Audit Log Directory Free Space Monitoring Percentage Thresholds Navigator Metadata Server monitoring settings.

Short Name: Audit Log Directory Free Space

This Navigator Metadata Server health test checks that the Auditing for the Navigator Metadata Server 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 Metadata Server process. This test can fail either because the Cloudera Audit Server is not accepting audits, or the Cloudera Manager Agent on the Navigator Metadata Server 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 Metadata Server monitoring setting.

Short Name: Audit Pipeline Test

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

Short Name: File Descriptors

This Navigator Metadata Server health test checks that the filesystem containing the heap dump directory of this Navigator Metadata Server 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 Navigator Metadata Server monitoring settings.

Short Name: Heap Dump Directory Free Space

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

Short Name: Host Health

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

Short Name: Log Directory Free Space

This is a Navigator Metadata Server health test that checks that the filesystem containing the Navigator Metadata Server Storage Dir of this Navigator Metadata Server has sufficient free space. See the Navigator Metadata Server Storage Dir description on the Navigator Metadata Server configuration page for more information on this directory type. This test can be configured using the Navigator Metadata Server Storage Dir Free Space Monitoring Absolute Thresholds and Navigator Metadata Server Storage Dir Free Space Monitoring Percentage Thresholds Navigator Metadata Server monitoring settings.

Short Name: Navigator Metadata Server Storage Dir Free Space

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

Short Name: Process Status

This alert indicates when the document count in the Navigator Elements Solr core is reaching Solrs maximum limit. Typically, the maximum number of documents in a Solr core is around 2 billion. When the document count reaches the critical threshold, Navigator Metadata Server will stop working. The warning threshold is set to give administrators time to reduce the volume of documents before Navigator can no longer function. Consider changing these thresholds if you want to give more time between when the alerts are triggered and when Navigator Metadata Server stops working. To reduce the number of documents, make sure Navigator purge is running regularly. For more information, see Troubleshooting Cloudera Navigator Metadata xServer

Short Name: Solr Element Count Threshold Test

This alert indicates when the document count in the Navigator Relations Solr core is reaching Solrs maximum limit. Typically, the maximum number of documents in a Solr core is around 2 billion. When the document count reaches the critical threshold, Navigator Metadata Server will stop working. The warning threshold is set to give administrators time to reduce the volume of documents before Navigator can no longer function. Consider changing these thresholds if you want to give more time between when the alerts are triggered and when Navigator Metadata Server stops working. To reduce the number of documents, make sure Navigator purge is running regularly. For more information, see Troubleshooting Cloudera Navigator Metadata Server

Short Name: Solr Relation Count Threshold Test

This Navigator Metadata Server 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 Metadata Server health test checks that the Navigator Metadata Server 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 Metadata Server monitoring settings.

Short Name: Unexpected Exits