5.6.2. HBase Master process

This alert is triggered if the HBase master 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 HBase master process is down

  • The HBase master has shut itself down because there were problems in the dependent services, ZooKeeper or HDFS

  • The Nagios server cannot connect to the HBase master through the network Possible remedies
  • Check the dependent services.

  • Look at the master log files (usually /var/log/hbase/*.log) for further information

  • Look at the configuration files (/etc/hbase/conf)

    Use ping to check the network connection between the Nagios server and the HBase master

  • Restart the master

loading table of contents...