@albert0087 Are you using OpenTSDB's asynchbase client to try to connect to our hbase? If yes, make sure you are setting the configurations correctly as per https://opentsdb.github.io/asynchbase/docs/build/html/authentication.html ... View more

@iamlazycoder As you have only a single Datanode, the blockplacement policy won't allow putting the second replica on the same Datanode.   You can try to put the file with a single replica and check.   hdfs dfs -Ddfs.replication=1 -put /path/to/local/file /path/to/hdfs/dir   Or you can change the dfs.replication in hdfs-site.xml to 1 at a cluster level.  ... View more

Hi @BrianChan Both the alerts are related. The checkpointing is done by the Standby Namenode and if it's not functioning properly, then the checkpoint process is not done and you will see those alerts.   You can go through the logs of the Standby Namenode and check why the checkpoint thread is stopped. Maybe the Standby Namenode is down? So you may want to restart the Standby Namenode to fix this. ... View more

If the same Node is getting down every time, it's worth checking the Memory utilization at the OS end. You can check the /var/log/messages of the NN host when the NN went down and check if the process is getting killed by an oom. ... View more

@RammiSE Try the below :   ./hbase hbck -j /tmp/hbase-hbck2-1.2.0.jar assigns -o f0b4865fe8ea07321ed8eb237a592c10 ... View more

@RammiSE you will need to assign the respective namespace region ID by checking the Hbase Master log using the hbck2 jar ... View more

Hi @RammiSE , Based on the exception, the hbase:namespace table is not online. You will need to assign the namespace region to bring up the Hbase Master.   https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/admin_hbase_hbck.html   ~~~ Caused by: java.io.IOException: Timedout 300000ms waiting for namespace table to be assigned and enabled: tableName=hbase:namespace, state=ENABLED ... View more