Hbase: Namespace Manager and Quota Manager Async] master.HMaster: Namespace manager failed to start

From logs:
2018-05-24 18:06:07,615 INFO  [LruBlockCacheStatsExecutor] hfile.LruBlockCache: totalSize=832.83 KB, freeSize=791.09 MB, max=791.90 MB, blockCount=0, accesses
=0, hits=0, hitRatio=0, cachingAccesses=0, cachingHits=0, cachingHitsRatio=0,evictions=239, evicted=0, evictedPerRun=0.0
2018-05-24 18:06:50,133 ERROR [Init Namespace Manager and Quota Manager Async] master.HMaster: Namespace manager failed to start.
java.io.IOException: Timedout 2400000ms waiting for namespace table to be assigned
        at org.apache.hadoop.hbase.master.TableNamespaceManager.start(TableNamespaceManager.java:109)
        at org.apache.hadoop.hbase.master.HMaster$1.run(HMaster.java:1162)
        at java.lang.Thread.run(Thread.java:745)
2018-05-24 18:06:50,135 FATAL [Init Namespace Manager and Quota Manager Async] master.HMaster: Master server abort: loaded coprocessors are: []
2018-05-24 18:06:50,135 FATAL [Init Namespace Manager and Quota Manager Async] master.HMaster: Shutdown Master due to namespace manager failed to start.
java.io.IOException: Timedout 2400000ms waiting for namespace table to be assigned
        at org.apache.hadoop.hbase.master.TableNamespaceManager.start(TableNamespaceManager.java:109)
        at org.apache.hadoop.hbase.master.HMaster$1.run(HMaster.java:1162)
        at java.lang.Thread.run(Thread.java:745)
2018-05-24 18:06:50,135 INFO  [Init Namespace Manager and Quota Manager Async] regionserver.HRegionServer: STOPPED: Shutdown Master due to namespace manager f
ailed to start.
Observed extended cluster downtime due to HBase system tables not being assigned at cluster start up.
The default values for the following two parameters are too low:
hbase.regionserver.executor.openregion.threads (default: 3)
hbase.master.namespace.init.timeout (default: 300000)
We set hbase.regionserver.executor.openregion.threads=200 and 
hbase.master.namespace.init.timeout=2400000 in some case to work around HBASE
0 Comments

There are no comments yet

Leave a comment

Your email address will not be published. Required fields are marked *