DocsHortonworks Data Platform

 

 5.5.6. HistoryServer process

This host-level alert is triggered if the HistoryServer process cannot be established to be up and listening on the network for the configured critical threshold, given in seconds. It uses the Nagios check_tcp plugin.

 5.5.6.1. Potential causes

  • The HistoryServer process is down or not responding.

  • The HistoryServer is not down but is not listening to the correct network port/address.

  • The Nagios Server cannot connect to the HistoryServer.

 5.5.6.2. Possible remedies

  • Check for any errors in the HistoryServer logs (/var/log/hadoop/mapred) and restart the HistoryServer, if necessary.

  • Use ping to check the network connection between the Nagios Server and the HistoryServer host.

Legal notices
loading table of contents...