[jira] [Comment Edited] (HBASE-17861) Regionserver down when checking the permission of staging dir if hbase.rootdir is on S3

["Yi Liang (JIRA)" <ji...@apache.org>]

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

Yi Liang edited comment on HBASE-17861 at 3/31/17 8:21 PM:
-----------------------------------------------------------

And in our master branch, the code in SecureBulkLoadEndpoint has been refactored, and the statement check the staging folder permission is removed. so the patch is only for branch-1.0



was (Author: easyliangjob):
And in our master branch, the code in SecureBulkLoadEndpoint has been refactored, and the statement check the folder permission is removed. so the patch is only for branch-1.0


> Regionserver down when checking the permission of staging dir if hbase.rootdir is on S3
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-17861
>                 URL: https://issues.apache.org/jira/browse/HBASE-17861
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Yi Liang
>            Assignee: Yi Liang
>             Fix For: 1.4.0
>
>         Attachments: HBASE-17861-V1.patch
>
>
> Found some issue, when set up HBASE-17437: Support specifying a WAL directory outside of the root directory.
> The region server are  showdown when I add following config into hbase-site.xml 
> hbase.rootdir = hdfs://xx/xx
> hbase.wal.dir = s3a://xx//xx
> hbase.coprocessor.region.classes = org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint
> Error is below
> {noformat}
> org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint threw java.lang.IllegalStateException: Directory already exists but permissions aren't set to '-rwx--x--x'
> {noformat}
> The reason is that, when hbase enable securebulkload, hbase will create a folder in s3, it can not set above permission, because in s3, all files are listed as having full read/write permissions and all directories appear to have full rwx permissions.  See simulated permission section in https://docs.hortonworks.com/HDPDocuments/HDCloudAWS/HDCloudAWS-1.8.0/bk_hdcloud-aws/content/s3-s3aclient/index.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)