hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matteo Bertozzi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-15790) Force "hbase" ownership on bulkload
Date Tue, 24 May 2016 01:10:13 GMT

     [ https://issues.apache.org/jira/browse/HBASE-15790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Matteo Bertozzi updated HBASE-15790:
    Attachment: HBASE-15790-v3.patch

yeah you are right. I tested with various configuration and looks like no user aside superuser
can change ownership.
systest can't chown to hbase
hbase can't chown to hbase a file owned by systest

SecureBulkLoadEndpoint seems to always do the chmod 777. so we are good in that case even
if the files are owned by someone that is not hbase.
I changed the patch in v3. to check for 777 permission. and if not try to do a chown. if not
able it will print a message telling the user what to do. 
(We have a bunch of cases of files not owned by hbase and with not enough permission that
end up getting the cluster stuck, so in theory this will improve a bit the situation)

> Force "hbase" ownership on bulkload
> -----------------------------------
>                 Key: HBASE-15790
>                 URL: https://issues.apache.org/jira/browse/HBASE-15790
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 2.0.0, 1.2.1, 1.1.4, 0.98.19
>            Reporter: Matteo Bertozzi
>            Assignee: Matteo Bertozzi
>            Priority: Minor
>         Attachments: HBASE-15790-v0.patch, HBASE-15790-v1.patch, HBASE-15790-v2.patch,
> When a user different than "hbase" bulkload files, in general we end up with files owned
by a user different than hbase. sometimes this causes problems with hbase not be able to move
files around archiving/deleting.
> A simple solution is probably to change the ownership of the files to "hbase" during

This message was sent by Atlassian JIRA

View raw message