HBase table (manual)

The error message could be an issue with the ZooKeeper configuration or HBase’s connection to Zookeeper. HBase uses Apache ZooKeeper to manage coordination between the HBase master and regionservers. You can try to resolve the issue first by checking the logs for both HBase and ZooKeeper for any specific error messages that might provide more insights into the issue. Look for log entries indicating that HBase is running and that the regionservers are communicating with the master node. You can view the current HBase logs by using SSH to connect to the master node, and navigating to the /var/log/hbase directory.

Make sure the HBase Master is running. You can check the HBase master status using the HBase shell command. You can use the command sudo service hbase-master status to check if the HBase service is running. If the service is running, you should see a message indicating that the service is active (running).

Check also the ZooKeeper configuration and ensure that ZooKeeper is running and properly configured on your EMR cluster. Verify the ZooKeeper Quorum settings in your HBase configuration. The ‘hbasesite.xml’ file should contain the correct ZooKeeper quorum settings. Use the command sudo service zookeeper status to check the status of the ZooKeeper service. If the service is running, you should see a message indicating that the service is active (running).

Also ensure that there are no firewall rules or network issues blocking the communication between your EMR cluster and Zookeeper.

For further reference: Amazon EMR Release Guide

ZooKeeper