[ 
https://issues.apache.org/jira/browse/HBASE-16178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363202#comment-15363202
 ] 

Dima Spivak commented on HBASE-16178:
-------------------------------------

This doesn't seem to be a bug in HBase. HDFS doesn't allow copying between 
encryption zones (or from a location that's not in an encryption zone into one 
that is), and it looks like you're trying to do a bulk load of HFiles that 
aren't in encryption zone into an HBase root directory that is. Since it looks 
like you're using HDP, it might be easiest to get help from a Hortonworks user 
forum.

> HBase restore command fails on cluster with encrypted HDFS
> ----------------------------------------------------------
>
>                 Key: HBASE-16178
>                 URL: https://issues.apache.org/jira/browse/HBASE-16178
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>         Environment: Cluster with Encrypted HDFS
>            Reporter: Romil Choksi
>              Labels: restore
>
> HBase restore command fails to move hfile into an encryption zone
> {code:title= HDFS namenode log}
> 2016-07-05 07:27:00,580 INFO  ipc.Server (Server.java:logException(2401)) - 
> IPC Server handler 31 on 8020, call 
> org.apache.hadoop.hdfs.protocol.ClientProtocol.rename from <ip_address>:53481 
> Call#130 Retry#0
> java.io.IOException: 
> /apps/hbase/staging/hbase__table_29ov3nxj1o__7o65g4lakspqe1mlku17g0n6e2c61v72o632puuntpfcf3tf41n69bfaso00gvlp/cf1/8cf0242072534ee0a7ee8710b9235c3e
>  can't be moved into an encryption zone.
>         at 
> org.apache.hadoop.hdfs.server.namenode.EncryptionZoneManager.checkMoveValidity(EncryptionZoneManager.java:272)
>         at 
> org.apache.hadoop.hdfs.server.namenode.FSDirRenameOp.unprotectedRenameTo(FSDirRenameOp.java:187)
>         at 
> org.apache.hadoop.hdfs.server.namenode.FSDirRenameOp.renameTo(FSDirRenameOp.java:474)
>         at 
> org.apache.hadoop.hdfs.server.namenode.FSDirRenameOp.renameToInt(FSDirRenameOp.java:73)
>         at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.renameTo(FSNamesystem.java:3761)
>         at 
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.rename(NameNodeRpcServer.java:986)
>         at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.rename(ClientNamenodeProtocolServerSideTranslatorPB.java:583)
>         at 
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
>         at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:640)
>         at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:982)
>         at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2313)
>         at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2309)
>         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:1724)
>         at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2307)
> {code}



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

Reply via email to