5.6.5. RegionServer process

This host-level alert is triggered if the RegionServer processes cannot be confirmed to be up and listening on the network for the configured critical threshold, given in seconds. It uses the Nagios check_tcp plug-in. Potential causes
  • The RegionServer process is down on the host

  • The RegionServer process is up and running but not listening on the correct network port (default 60030).

  • The Nagios server cannot connect to the RegionServer through the network. Possible remedies
  • Check for any errors in the logs (/var/log/hbase/) and restart the RegionServer process using Ambari Web.

  • Run the netstat-tuplpn command to check if the RegionServer process is bound to the correct network port.

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

loading table of contents...