[
https://issues.apache.org/jira/browse/HBASE-17861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954502#comment-15954502
]
Yi Liang commented on HBASE-17861:
----------------------------------
Hi Ted, thanks for review, the reason why I did not use set is
(1) In java, When we initialize set, we still need to initialize as below,
transform a array to set; or we use add() method for multiple times to add
values. It seems not very efficient
Set<String> h = new HashSet<String>(Arrays.asList("a", "b")); or h.add(a);
h.add(b);
(2) In the code, in the check
condition(scheme.startsWith(FsNotSupportPermission[i])), I use startwith()
method, since there are schemes like: s3a, s3, s3n, wasb, wasbs and so on, the
Set.contains(FsNotSupportPermission[i]) method seems does not work quite well
in our case.
Let me know if you have any good idea to implement it, thanks, :)
> 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.branch-1.V1.patch,
> HBASE-17861.branch-1.V2.patch, HBASE-17861.branch-1.V3.patch,
> 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 = s3a://xx//xx
> hbase.wal.dir = hdfs://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)
