[
https://issues.apache.org/jira/browse/HBASE-8495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-8495:
-------------------------
Fix Version/s: (was: 0.95.2)
0.96.0
> Change ownership of the directory to bulk load
> ----------------------------------------------
>
> Key: HBASE-8495
> URL: https://issues.apache.org/jira/browse/HBASE-8495
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Affects Versions: 0.94.7, 0.95.0
> Reporter: Matteo Bertozzi
> Priority: Trivial
> Fix For: 0.96.0
>
>
> To bulk load something you need to change the ownership of the data directory
> to allow the hbase user to read and move the files, also in the split case
> you must use the hbase user to run the LoadIncrementalHFiles tool, since
> internally some directories "_tmp" are created to add the split reference
> files.
> In a secure cluster, the SecureBulkLoadEndPoint will take care of this
> problem by doing a chmod 777 on the directory to bulk load.
> NOTE that a chown is not possible since you must be a super user to change
> the ownership, a change group may be possible but the user must be in the
> hbase group... and anyway it will require a chmod to allow the group to
> perform the move.
> {code}
> Caused by: org.apache.hadoop.security.AccessControlException: Permission
> denied: user=hbase, access=WRITE, inode="/test/cf":th30z:supergroup:drwxr-xr-x
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:205)
> Caused by:
> org.apache.hadoop.hbase.ipc.RemoteWithExtrasException(java.io.IOException):
> java.io.IOException: Exception in rename
> at
> org.apache.hadoop.hbase.regionserver.HRegionFileSystem.rename(HRegionFileSystem.java:928)
> at
> org.apache.hadoop.hbase.regionserver.HRegionFileSystem.commitStoreFile(HRegionFileSystem.java:340)
> at
> org.apache.hadoop.hbase.regionserver.HRegionFileSystem.bulkLoadStoreFile(HRegionFileSystem.java:414)
> {code}
--
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
