Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

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

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

Expert Contributor

hbase(main):001:0> create 'emp','c1'

SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/DBHADOOP/installations/hbase-0.98.1-hadoop2/lib/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/DBHADOOP/installations/hadoop-2.4.0/share/hadoop/common/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

ERROR: java.io.IOException: Table Namespace Manager not ready yet, try again later at org.apache.hadoop.hbase.master.HMaster.getNamespaceDescriptor(HMaster.java:3187) at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1743) at org.apache.hadoop.hbase.master.HMaster.createTable(HMaster.java:1782) at org.apache.hadoop.hbase.protobuf.generated.MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:40470) at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2012) at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98) at org.apache.hadoop.hbase.ipc.FifoRpcScheduler$1.run(FifoRpcScheduler.java:73) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)

8 REPLIES 8

Re: HBASE issue : java.io.IOException: Table Namespace Manager not ready yet, try again later

can you check hbase master and regionserver logs for errors.

Re: HBASE issue : java.io.IOException: Table Namespace Manager not ready yet, try again later

Contributor

@Amit,

You can use file system check for HBase and check consistencies and inconsistencies,

hbase hbck

If there are some incosistencies present you can try to repair them by,

hbase hbck -fix

Re: HBASE issue : java.io.IOException: Table Namespace Manager not ready yet, try again later

To clarify on Nitin's point: the hbase:namespace table is likely not online. You can use the HBase master and regionserver logs, as well as the HBase web UIs to pinpoint exactly why this is.

Re: HBASE issue : java.io.IOException: Table Namespace Manager not ready yet, try again later

Expert Contributor

@Josh Elser Where I can find HBase master and regionserver logs

Re: HBASE issue : java.io.IOException: Table Namespace Manager not ready yet, try again later

Expert Contributor
Log file :

2016-11-01 23:03:46,688 DEBUG [CDCUDHDPDB3,60000,1477398007087.splitLogManagerTimeoutMonitor] master.SplitLogManager: resubmitting unassigned task(s) after timeout
2016-11-01 23:03:46,688 DEBUG [main-EventThread] master.SplitLogManager: task not yet acquired /hbase/splitWAL/WALs%2FCDCUDHDPDB1%2C60020%2C1475214696961-splitting%2FCDCUDHDPDB1%252C60020%252C1475214696961.1477245151900.meta ver = 1
2016-11-01 23:03:46,691 INFO  [main-EventThread] master.SplitLogManager: task /hbase/splitWAL/RESCAN0000010860 entered state: DONE CDCUDHDPDB3,60000,1477398007087
2016-11-01 23:03:46,693 DEBUG [main-EventThread] master.SplitLogManager$DeleteAsyncCallback: deleted /hbase/splitWAL/RESCAN0000010860
2016-11-01 23:03:46,693 DEBUG [main-EventThread] master.SplitLogManager: deleted task without in memory state /hbase/splitWAL/RESCAN0000010860
2016-11-01 23:03:46,911 INFO  [master:CDCUDHDPDB3:60000] master.ServerManager: Waiting for region servers count to settle; currently checked in 0, slept for 623597327 ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms, interval of 1500 ms.
2016-11-01 23:03:48,414 INFO  [master:CDCUDHDPDB3:60000] master.ServerManager: Waiting for region servers count to settle; currently checked in 0, slept for 623598830 ms, expecting minimum of 1, maximum of 2147483647, timeout of 4500 ms, interval of 1500 ms.
2016-11-01 23:03:48,687 INFO  [CDCUDHDPDB3,60000,1477398007087.splitLogManagerTimeoutMonitor] master.SplitLogManager: total tasks = 1 unassigned = 1 tasks={/hbase/splitWAL/WALs%2FCDCUDHDPDB1%2C60020%2C1475214696961-splitting%2FCDCUDHDPDB1%252C60020%252C1475214696961.1477245151900.meta=last_update = 1477398029350 last_version = -1 cur_worker_name = null status = in_progress incarnation = 1 resubmits = 0 batch = null}


Re: HBASE issue : java.io.IOException: Table Namespace Manager not ready yet, try again later

Expert Contributor

This issue is solved now .

Re: HBASE issue : java.io.IOException: Table Namespace Manager not ready yet, try again later

Expert Contributor

Hi @Amit Dass, how did you solve this issue?

Re: HBASE issue : java.io.IOException: Table Namespace Manager not ready yet, try again later

New Contributor

It working

Details can be found here: Running hbck to identify inconsistencies

Don't have an account?
Coming from Hortonworks? Activate your account here