You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Yi Liang (JIRA)" <ji...@apache.org> on 2017/03/31 20:18:41 UTC
[jira] [Created] (HBASE-17861) Regionserver down when checking the
permission of staging dir if hbase.rootdir is on S3
Yi Liang created HBASE-17861:
--------------------------------
Summary: 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
Reporter: Yi Liang
Assignee: Yi Liang
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)