You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Stephen Yuan Jiang (JIRA)" <ji...@apache.org> on 2015/06/18 19:44:01 UTC

[jira] [Created] (HBASE-13935) Orphaned namespace table ZK node should not prevent master to start

Stephen Yuan Jiang created HBASE-13935:
------------------------------------------

             Summary: Orphaned namespace table ZK node should not prevent master to start
                 Key: HBASE-13935
                 URL: https://issues.apache.org/jira/browse/HBASE-13935
             Project: HBase
          Issue Type: Bug
          Components: master
    Affects Versions: 0.98.13, 1.0.0
            Reporter: Stephen Yuan Jiang
            Assignee: Stephen Yuan Jiang


Before we have the state-of-art Procedure V2 feature (HBASE 1.0 release or older), we frequently see the following issue (orphaned ZK node) that prevent master to start (at least in testing):
{noformat}
2015-06-16 17:54:36,472 FATAL [master:10.0.0.99:60000] master.HMaster: Unhandled exception. Starting shutdown.
org.apache.hadoop.hbase.TableExistsException: hbase:namespace
	at org.apache.hadoop.hbase.master.handler.CreateTableHandler.prepare(CreateTableHandler.java:137)
	at org.apache.hadoop.hbase.master.TableNamespaceManager.createNamespaceTable(TableNamespaceManager.java:232)
	at org.apache.hadoop.hbase.master.TableNamespaceManager.start(TableNamespaceManager.java:86)
	at org.apache.hadoop.hbase.master.HMaster.initNamespace(HMaster.java:1123)
	at org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:947)
	at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:618)
	at java.lang.Thread.run(Thread.java:745)
2015-06-16 17:54:36,472 INFO  [master:10.0.0.99:60000] master.HMaster: Aborting
{noformat}

The above call trace is from a 0.98.x test run.  We saw similar issue in 1.0.x run, too.  

The proposed fix is to ignore the zk node and force namespace table creation to be complete so that master can start successfully.  






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)