hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yi Liang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17861) Regionserver down when checking the permission of staging dir if hbase.rootdir is on S3
Date Fri, 31 Mar 2017 22:44:41 GMT

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

Yi Liang commented on HBASE-17861:
----------------------------------

>From Enis comment in HBASE-11045:
[[HBase is supported (to the extend that corresponding vendors support it) on a couple of
file systems other than HDFS: gpfs, maprfs, EMC Isilon, Microsoft WASB are the ones from the
top of my head. You should contact the corresponding vendor if you want to learn more. ]]

And I just check Microsoft WASB, it seems it does not support permission, see https://hadoop.apache.org/docs/stable/hadoop-azure/index.html.
 It says "File owner and group are persisted, but the permissions model is not enforced. Authorization
occurs at the level of the entire Azure Blob Storage account."

I probably could not cover all the above FS

> 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
>              Labels: filesystem, s3, wal
>             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 Object stores have
differerent authorization models in https://hadoop.apache.org/docs/current3/hadoop-aws/tools/hadoop-aws/index.html



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

Mime
View raw message