Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Inconsistencies resulting in my inability to create tables in Hbase

avatar
New Contributor

Hello 
i have the following problems  when i use hbase hbck

 


10 inconsistencies detected.
Status: INCONSISTENT
2023-02-01 13:51:01,346 INFO [main] zookeeper.ZooKeeper: Session: 0x1860d1d2ec00091 closed
2023-02-01 13:51:01,346 INFO [main] client.ConnectionManager$HConnectionImplementation: Closing master protocol: MasterService
2023-02-01 13:51:01,346 INFO [main] client.ConnectionManager$HConnectionImplementation: Closing zookeeper sessionid=0x1860d1d2ec00092
2023-02-01 13:51:01,346 INFO [main-EventThread] zookeeper.ClientCnxn: EventThread shut down
2023-02-01 13:51:01,349 INFO [main] zookeeper.ZooKeeper: Session: 0x1860d1d2ec00092 closed
2023-02-01 13:51:01,349 INFO [main-EventThread] zookeeper.ClientCnxn: EventThread shut down

 

Also am unable to create a new table and this is the message that is being displayed  when i use 

create 'users','userinfo'

ERROR: java.io.IOException: Table Namespace Manager not ready yet, try again later

 

1 ACCEPTED SOLUTION

avatar
Super Collaborator

Hello @Menyawy 

 

Thanks for using Cloudera Community. The Error [1] indicates your Team is using CDH v5.x using HBase v1.x. In the concerned release, We have limited choices to ensure "hbase:namespace" Table Region is assigned correctly as shared below:

 

(I) Easier Yet Not-Always-Successful Option:

1) Shutdown HBase Service 
2) echo "rmr /hbase" | hbase zkcli (From HMaster Node) 
3) Start HBase Service 
4) sudo hbase hbase hbck -fixAssignments

(II) Review whether any of the "hbase:namespace" Table Region files are reporting MissingBlockException. If Yes, We need to fix the MissingBlockException.

(III) Possible for the RegionServer Logs (Wherein the "hbase:namespace" Table Region is being assigned) would offer additional insight into the reasoning for the RegionServer being Unable to assign the "hbase:namespace" Table Region successfully. Your Team may review the concerned RegionServer Logs as well.

 

There may be Other Options, yet such Inconsistencies are better handled in HBase 2.x [1] & your Team should plan for using HBase v2.x soon.

 

Regards, Smarak

 

[1] https://github.com/apache/hbase-operator-tools/blob/master/hbase-hbck2/README.md#master-startup-cann...

View solution in original post

1 REPLY 1

avatar
Super Collaborator

Hello @Menyawy 

 

Thanks for using Cloudera Community. The Error [1] indicates your Team is using CDH v5.x using HBase v1.x. In the concerned release, We have limited choices to ensure "hbase:namespace" Table Region is assigned correctly as shared below:

 

(I) Easier Yet Not-Always-Successful Option:

1) Shutdown HBase Service 
2) echo "rmr /hbase" | hbase zkcli (From HMaster Node) 
3) Start HBase Service 
4) sudo hbase hbase hbck -fixAssignments

(II) Review whether any of the "hbase:namespace" Table Region files are reporting MissingBlockException. If Yes, We need to fix the MissingBlockException.

(III) Possible for the RegionServer Logs (Wherein the "hbase:namespace" Table Region is being assigned) would offer additional insight into the reasoning for the RegionServer being Unable to assign the "hbase:namespace" Table Region successfully. Your Team may review the concerned RegionServer Logs as well.

 

There may be Other Options, yet such Inconsistencies are better handled in HBase 2.x [1] & your Team should plan for using HBase v2.x soon.

 

Regards, Smarak

 

[1] https://github.com/apache/hbase-operator-tools/blob/master/hbase-hbck2/README.md#master-startup-cann...