You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2013/02/05 02:19:11 UTC

[jira] [Created] (HBASE-7766) master cannot go from 94 to 96 due to zookeeper data

Sergey Shelukhin created HBASE-7766:
---------------------------------------

             Summary: master cannot go from 94 to 96 due to zookeeper data
                 Key: HBASE-7766
                 URL: https://issues.apache.org/jira/browse/HBASE-7766
             Project: HBase
          Issue Type: Bug
            Reporter: Sergey Shelukhin


After running a 94 cluster and then updating it to 96, master cannot start due to the following:

2013-02-04 19:59:15,494 FATAL org.apache.hadoop.hbase.master.HMaster: Unhandled exception. Starting shutdown.
org.apache.zookeeper.KeeperException$DataInconsistencyException: KeeperErrorCode = DataInconsistency
at org.apache.hadoop.hbase.zookeeper.ZKUtil.convert(ZKUtil.java:1705)
at org.apache.hadoop.hbase.zookeeper.ZKTableReadOnly.getTableState(ZKTableReadOnly.java:158)
at org.apache.hadoop.hbase.zookeeper.ZKTable.populateTableStates(ZKTable.java:82)
at org.apache.hadoop.hbase.zookeeper.ZKTable.<init>(ZKTable.java:69)
at org.apache.hadoop.hbase.master.AssignmentManager.<init>(AssignmentManager.java:199)
at org.apache.hadoop.hbase.master.HMaster.initializeZKBasedSystemTrackers(HMaster.java:550)
at org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:671)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:476)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.hadoop.hbase.DeserializationException: Missing pb magic PBUF prefix
at org.apache.hadoop.hbase.protobuf.ProtobufUtil.expectPBMagicPrefix(ProtobufUtil.java:196)
at org.apache.hadoop.hbase.zookeeper.ZKTableReadOnly.getTableState(ZKTableReadOnly.java:148)
... 7 more

It should probably nuke the data and start as with blanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira