Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 9 Sep 2014 18:50:30 +0000 (UTC)
From: "David Schorow (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12646122.1367750011000.29891.1410288630013@Atlassian.JIRA>
In-Reply-To: <JIRA.12646122.1367750011000@Atlassian.JIRA>
References: <JIRA.12646122.1367750011000@Atlassian.JIRA>
 <JIRA.12646122.1367750011021@arcas>
Subject: [jira] [Commented] (HBASE-8495) Change ownership of the directory
 to bulk load
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

David Schorow commented on HBASE-8495:
--------------------------------------

bq. I'm planning to do the similar for un-secure case ...
Is that going to be in a new Jira, since this one is closed?

> 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
>            Assignee: Matteo Bertozzi
>            Priority: Trivial
>             Fix For: 0.99.0, 0.94.21, 0.98.4
>
>         Attachments: HBASE-8495-0.94-v0.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)