[
https://issues.apache.org/jira/browse/HBASE-15790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274640#comment-15274640
]
Jonathan Hsieh commented on HBASE-15790:
----------------------------------------
lgtm if the bot passes.
Seems like there could be rare race between 497/498 if there was a crash.
Probably not worth fixing, but might be worth filing a follow up for hbck to
check file owners/groups and perms to find things that seem strange. Wdyt?
{code}
public Void run() throws Exception {
496 FsPermission perms = FSUtils.getFilePermissions(fs, conf,
HConstants.DATA_FILE_UMASK_KEY);
497 fs.setOwner(dstPath, filesOwner, filesGroup);
498 fs.setPermission(dstPath, perms);
499 return null;
500 }
{code}
> 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
>
>
> 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 bulkload.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
