You can either give user hbase write access to /apps, or use another directory where user hbase can write to.
Cheers On Wed, Apr 9, 2014 at 6:28 PM, Artem Ervits <[email protected]> wrote: > 2014-03-21 11:35:36,998 FATAL [master:server:60000] master.HMaster: > Unhandled exception. Starting shutdown. > org.apache.hadoop.security.AccessControlException: Permission denied: > user=hbase, access=WRITE, inode="/apps":hdfs:hdfs:drwxr-xr-x > at > org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:234) > at > org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:214) > at > org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:158) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkPermission(FSNamesystem.java:5202) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkPermission(FSNamesystem.java:5184) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkAncestorAccess(FSNamesystem.java:5158) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.mkdirsInternal(FSNamesystem.java:3405) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.mkdirsInt(FSNamesystem.java:3375) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.mkdirs(FSNamesystem.java:3349) > at > org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.mkdirs(NameNodeRpcServer.java:724) > at > org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.mkdirs(ClientNamenodeProtocolServerSideTranslatorPB.java:502) > at > org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java:59598) > at > org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:585) > at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:928) > at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2053) > at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2049) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1491) > at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2047) > > -----Original Message----- > From: Artem Ervits > Sent: Wednesday, April 09, 2014 5:58 PM > To: '[email protected]' > Subject: Re: restore snapshot on another cluster > > I read it thanks. I'm getting privilege access exception hbase user on > write permission. I don't have the exception handy. I will supply it > shortly. I'm using 0.96.1.1 on hadoop 2. > > > Artem Ervits > Data Analyst > New York Presbyterian Hospital > > ----- Original Message ----- > From: Ted Yu [mailto:[email protected]] > Sent: Wednesday, April 09, 2014 05:48 PM > To: [email protected] <[email protected]> > Subject: Re: restore snapshot on another cluster > > Can you give us some more detail such as: > > the HBase release you're using > the stack trace of permission error > > I assume you have read 15.8.7 and 15.8.8 of: > http://hbase.apache.org/book.html#ops.snapshots > > Cheers > > > On Wed, Apr 9, 2014 at 3:08 PM, Artem Ervits <[email protected]> wrote: > > > Hello all, > > > > When I take a snapshot on cluster 1, copy it to cluster 2 using > > ExportSnapshot utility, what permissions should I set on the snapshot > > to be able to clone it into a new table? I matched the permissions of > > the external snapshot to the permissions of any local snapshots on > > cluster 2 and still get hbase user write permission errors. Am I missing > something? > > > > Thanks > > > > ________________________________ > > > > This electronic message is intended to be for the use only of the > > named recipient, and may contain information that is confidential or > privileged. > > If you are not the intended recipient, you are hereby notified that > > any disclosure, copying, distribution or use of the contents of this > > message is strictly prohibited. If you have received this message in > > error or are not the named recipient, please notify us immediately by > > contacting the sender at the electronic mail address noted above, and > > delete and destroy all copies of this message. Thank you. > > > > This electronic message is intended to be for the use only of the > > named recipient, and may contain information that is confidential or > privileged. > > If you are not the intended recipient, you are hereby notified that > > any disclosure, copying, distribution or use of the contents of this > > message is strictly prohibited. If you have received this message in > > error or are not the named recipient, please notify us immediately by > > contacting the sender at the electronic mail address noted above, and > > delete and destroy all copies of this message. Thank you. > > ________________________________ > > This electronic message is intended to be for the use only of the named > recipient, and may contain information that is confidential or privileged. > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution or use of the contents of this message is > strictly prohibited. If you have received this message in error or are not > the named recipient, please notify us immediately by contacting the sender > at the electronic mail address noted above, and delete and destroy all > copies of this message. Thank you. > > This electronic message is intended to be for the use only of the named > recipient, and may contain information that is confidential or privileged. > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution or use of the contents of this message is > strictly prohibited. If you have received this message in error or are not > the named recipient, please notify us immediately by contacting the sender > at the electronic mail address noted above, and delete and destroy all > copies of this message. Thank you. >
