History Server Health Tests

History Server File Descriptors

This History Server health test checks that the number of file descriptors used does not rise above some percentage of the History 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 History Server 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.	spark_history_server_fd_thresholds	critical:70.0, warning:50.0	PERCENT

History Server Host Health

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

Short Name: Host Health

Property Name	Description	Template Name	Default Value	Unit
History Server Host Health Test	When computing the overall History Server health, consider the host's health.	spark_history_server_host_health_enabled	true	no unit

History Server Log Directory Free Space

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

Short Name: Log Directory Free Space

Property Name	Description	Template Name	Default Value	Unit
Log Directory Free Space Monitoring Absolute Thresholds	The health test thresholds for monitoring of free space on the filesystem that contains this role's log directory.	log_directory_free_space_absolute_thresholds	critical:5.36870912E9, warning:1.073741824E10	BYTES
Log Directory Free Space Monitoring Percentage Thresholds	The health test thresholds for monitoring of free space on the filesystem that contains this role's log directory. Specified as a percentage of the capacity on that filesystem. This setting is not used if a Log Directory Free Space Monitoring Absolute Thresholds setting is configured.	log_directory_free_space_percentage_thresholds	critical:never, warning:never	PERCENT

History Server Process Status

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

Short Name: Process Status

Property Name	Description	Template Name	Default Value	Unit
History Server Process Health Test	Enables the health test that the History Server's process state is consistent with the role configuration	spark_history_server_scm_health_enabled	true	no unit

History Server Unexpected Exits

This History Server health test checks that the History 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 History Server 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