You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Jerry He <je...@gmail.com> on 2014/04/21 06:14:39 UTC
acl data on zookeeper after migration from hbase 0.94 to 0.96
Hi,
While testing migration from 0.94 to 0.96 with security enabled, I got the
following exception and hbase master failed to start.
The master TableAuthManager was trying to fresh from the acl node on
zookeeper.
The acl data on zookeeper (old acl data from 0.94) seems to be corrupted.
My HBase upgrade is together with hdfs and zookeeper upgrades.
Before I figure out why the acl data is not readable, I wonder if we still
need the old acl data from 0.94 on zookeeper.
During migration96, we migrate the acl data in meta table, but don't clean
the acl node.
The acl data in meta table is all we need, right?
2014-04-16 08:52:41,625 ERROR
org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration:
Error in readFields
java.io.EOFException
at java.io.DataInputStream.readBoolean(DataInputStream.java:238)
at org.apache.hadoop.hbase.security.access.TablePermission.readFields
(TablePermission.java:397)
at
org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration.readObject
(HbaseObjectWritableFor96Migration.java:689)
at
org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration.readObject
(HbaseObjectWritableFor96Migration.java:589)
at
org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration.readObject
(HbaseObjectWritableFor96Migration.java:650)
at
org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration.readObject
(HbaseObjectWritableFor96Migration.java:589)
at
org.apache.hadoop.hbase.security.access.AccessControlLists.readPermissions
(AccessControlLists.java:614)
at
org.apache.hadoop.hbase.security.access.TableAuthManager.refreshTableCacheFromWritable
(TableAuthManager.java:158)
at
org.apache.hadoop.hbase.security.access.ZKPermissionWatcher.refreshAuthManager
(ZKPermissionWatcher.java:152)
at org.apache.hadoop.hbase.security.access.ZKPermissionWatcher.refreshNodes
(ZKPermissionWatcher.java:135)
at org.apache.hadoop.hbase.security.access.ZKPermissionWatcher.start
(ZKPermissionWatcher.java:64)
at org.apache.hadoop.hbase.security.access.TableAuthManager.<init>
(TableAuthManager.java:114)
at org.apache.hadoop.hbase.security.access.TableAuthManager.get
(TableAuthManager.java:662)
at org.apache.hadoop.hbase.security.access.AccessController.start
(AccessController.java:525)
at org.apache.hadoop.hbase.coprocessor.CoprocessorHost$Environment.startup
(CoprocessorHost.java:634)
at org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadInstance
(CoprocessorHost.java:258)
at
org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadSystemCoprocessors
(CoprocessorHost.java:158)
at org.apache.hadoop.hbase.master.MasterCoprocessorHost.<init>
(MasterCoprocessorHost.java:69)
at org.apache.hadoop.hbase.master.HMaster.finishInitialization
(HMaster.java:827)
at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:612)
Re: acl data on zookeeper after migration from hbase 0.94 to 0.96
Posted by Jerry He <je...@gmail.com>.
Great! Thanks, Jeffrey. We are at an early version of 0.96.
On Apr 21, 2014 9:47 AM, "Jeffrey Zhong" <jz...@hortonworks.com> wrote:
>
> Which Hbase version you're upgrading to? The issue should be fixed in
> HBASE-10581.
>
> On 4/20/14 9:14 PM, "Jerry He" <je...@gmail.com> wrote:
>
> >Hi,
> >
> >While testing migration from 0.94 to 0.96 with security enabled, I got the
> >following exception and hbase master failed to start.
> >The master TableAuthManager was trying to fresh from the acl node on
> >zookeeper.
> >The acl data on zookeeper (old acl data from 0.94) seems to be corrupted.
> >My HBase upgrade is together with hdfs and zookeeper upgrades.
> >Before I figure out why the acl data is not readable, I wonder if we still
> >need the old acl data from 0.94 on zookeeper.
> >During migration96, we migrate the acl data in meta table, but don't clean
> >the acl node.
> >The acl data in meta table is all we need, right?
> >
> >
> >2014-04-16 08:52:41,625 ERROR
> >org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration:
> >Error in readFields
> >java.io.EOFException
> >at java.io.DataInputStream.readBoolean(DataInputStream.java:238)
> >at org.apache.hadoop.hbase.security.access.TablePermission.readFields
> >(TablePermission.java:397)
> >at
> >org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration.
> >readObject
> >(HbaseObjectWritableFor96Migration.java:689)
> >at
> >org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration.
> >readObject
> >(HbaseObjectWritableFor96Migration.java:589)
> >at
> >org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration.
> >readObject
> >(HbaseObjectWritableFor96Migration.java:650)
> >at
> >org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration.
> >readObject
> >(HbaseObjectWritableFor96Migration.java:589)
> >at
> >org.apache.hadoop.hbase.security.access.AccessControlLists.readPermissions
> >(AccessControlLists.java:614)
> >at
> >org.apache.hadoop.hbase.security.access.TableAuthManager.refreshTableCache
> >FromWritable
> >(TableAuthManager.java:158)
> >at
> >org.apache.hadoop.hbase.security.access.ZKPermissionWatcher.refreshAuthMan
> >ager
> >(ZKPermissionWatcher.java:152)
> >at
> >org.apache.hadoop.hbase.security.access.ZKPermissionWatcher.refreshNodes
> >(ZKPermissionWatcher.java:135)
> >at org.apache.hadoop.hbase.security.access.ZKPermissionWatcher.start
> >(ZKPermissionWatcher.java:64)
> >at org.apache.hadoop.hbase.security.access.TableAuthManager.<init>
> >(TableAuthManager.java:114)
> >at org.apache.hadoop.hbase.security.access.TableAuthManager.get
> >(TableAuthManager.java:662)
> >at org.apache.hadoop.hbase.security.access.AccessController.start
> >(AccessController.java:525)
> >at org.apache.hadoop.hbase.coprocessor.CoprocessorHost$Environment.startup
> >(CoprocessorHost.java:634)
> >at org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadInstance
> >(CoprocessorHost.java:258)
> >at
> >org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadSystemCoprocessors
> >(CoprocessorHost.java:158)
> >at org.apache.hadoop.hbase.master.MasterCoprocessorHost.<init>
> >(MasterCoprocessorHost.java:69)
> >at org.apache.hadoop.hbase.master.HMaster.finishInitialization
> >(HMaster.java:827)
> >at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:612)
>
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
Re: acl data on zookeeper after migration from hbase 0.94 to 0.96
Posted by Jeffrey Zhong <jz...@hortonworks.com>.
Which Hbase version you're upgrading to? The issue should be fixed in
HBASE-10581.
On 4/20/14 9:14 PM, "Jerry He" <je...@gmail.com> wrote:
>Hi,
>
>While testing migration from 0.94 to 0.96 with security enabled, I got the
>following exception and hbase master failed to start.
>The master TableAuthManager was trying to fresh from the acl node on
>zookeeper.
>The acl data on zookeeper (old acl data from 0.94) seems to be corrupted.
>My HBase upgrade is together with hdfs and zookeeper upgrades.
>Before I figure out why the acl data is not readable, I wonder if we still
>need the old acl data from 0.94 on zookeeper.
>During migration96, we migrate the acl data in meta table, but don't clean
>the acl node.
>The acl data in meta table is all we need, right?
>
>
>2014-04-16 08:52:41,625 ERROR
>org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration:
>Error in readFields
>java.io.EOFException
>at java.io.DataInputStream.readBoolean(DataInputStream.java:238)
>at org.apache.hadoop.hbase.security.access.TablePermission.readFields
>(TablePermission.java:397)
>at
>org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration.
>readObject
>(HbaseObjectWritableFor96Migration.java:689)
>at
>org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration.
>readObject
>(HbaseObjectWritableFor96Migration.java:589)
>at
>org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration.
>readObject
>(HbaseObjectWritableFor96Migration.java:650)
>at
>org.apache.hadoop.hbase.security.access.HbaseObjectWritableFor96Migration.
>readObject
>(HbaseObjectWritableFor96Migration.java:589)
>at
>org.apache.hadoop.hbase.security.access.AccessControlLists.readPermissions
>(AccessControlLists.java:614)
>at
>org.apache.hadoop.hbase.security.access.TableAuthManager.refreshTableCache
>FromWritable
>(TableAuthManager.java:158)
>at
>org.apache.hadoop.hbase.security.access.ZKPermissionWatcher.refreshAuthMan
>ager
>(ZKPermissionWatcher.java:152)
>at
>org.apache.hadoop.hbase.security.access.ZKPermissionWatcher.refreshNodes
>(ZKPermissionWatcher.java:135)
>at org.apache.hadoop.hbase.security.access.ZKPermissionWatcher.start
>(ZKPermissionWatcher.java:64)
>at org.apache.hadoop.hbase.security.access.TableAuthManager.<init>
>(TableAuthManager.java:114)
>at org.apache.hadoop.hbase.security.access.TableAuthManager.get
>(TableAuthManager.java:662)
>at org.apache.hadoop.hbase.security.access.AccessController.start
>(AccessController.java:525)
>at org.apache.hadoop.hbase.coprocessor.CoprocessorHost$Environment.startup
>(CoprocessorHost.java:634)
>at org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadInstance
>(CoprocessorHost.java:258)
>at
>org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadSystemCoprocessors
>(CoprocessorHost.java:158)
>at org.apache.hadoop.hbase.master.MasterCoprocessorHost.<init>
>(MasterCoprocessorHost.java:69)
>at org.apache.hadoop.hbase.master.HMaster.finishInitialization
>(HMaster.java:827)
>at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:612)
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.