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

Short Name: File Descriptors

This Solr Server health test checks that the Solr Server 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 test may indicate a capacity planning problem or misconfiguration of the Solr Server. This test can be configured using the Garbage Collection Duration Thresholds and Garbage Collection Duration Monitoring Period Solr Server monitoring settings.

Short Name: GC Duration

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

Short Name: Host Health

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

Short Name: Log Directory Free Space

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

Short Name: Process Status

This is a Solr Server health test that checks that the Solr Server is responding quickly to API requests by the Cloudera Manager Agent to collect the status of the Solr Server's Solr cores. A failure of this health test may indicate a problem with the Solr Server, a misconfiguration of the Solr Server or a problem with the Cloudera Manager Agent. Consult the Cloudera Manager Agent logs and the logs of the Solr Server for more details. If the test's failure message indicates a communication problem, this means that the Cloudera Manager Agent's HTTP requests to the Solr Server are failing or timing out. These requests are completely local to the Solr Server's host, and so should never fail under normal conditions. If the test's failure message indicates an unexpected response, then the Solr 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 enabled or disabled using the Solr Server API Liveness Solr Server monitoring setting and can be configured using the Solr Server API Liveness Request Duration monitoring setting.

Short Name: Solr Server API Liveness

This Solr Server health test checks that the Solr Server has not recently exited unexpectedly. The test returns "Bad" health if the number of unexpected exits goes above a critical threshold. For example, if this test is configured with a critical threshold of 1, this test would return "Good" health if there have been no unexpected exits recently. If there has been 1 or more unexpected exits recently, this test would return "Bad" health. This test can be configured using the Unexpected Exits Thresholds and Unexpected Exits Monitoring Period Solr Server monitoring settings.

Short Name: Unexpected Exits

This Solr Server health test checks that the web server of the Solr Server 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 test may indicate a problem with the web server of the Solr Server, a misconfiguration of the Solr Server or a problem with the Cloudera Manager Agent. Consult the Cloudera Manager Agent logs and the logs of the Solr Server 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 Solr Server's web server are failing or timing out. These requests are completely local to the Solr Server's host, and so should never fail under normal conditions. If the test's failure message indicates an unexpected response, then the Solr Server'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 Solr Server monitoring setting.

Short Name: Web Server Status