5.4.3. HistoryServer CPU utilization

This host-level alert is triggered if the percent of CPU utilization on the HistoryServer exceeds the configured critical threshold. This alert uses the Nagios check_snmp_load plug-in.

 5.4.3.1. Potential causes
  • Unusually high CPU utilization: Can be caused by a very unusual job/query workload, but this is generally the sign of an issue in the daemon.

  • A down SNMP daemon on the HistoryServer node, producing an unknown status

 5.4.3.2. Possible remedies
  • Use the top command to determine which processes are consuming excess CPU.

  • Reset the offending process.

  • Check the status of the SNMP daemon.


loading table of contents...