[
https://issues.apache.org/jira/browse/HBASE-18512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585730#comment-16585730
]
Hudson commented on HBASE-18512:
--------------------------------
Results for branch branch-1.3
[build #433 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/433/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/433//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/433//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/433//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
> Region Server will abort with IllegalStateException if HDFS umask has limited
> scope
> -----------------------------------------------------------------------------------
>
> Key: HBASE-18512
> URL: https://issues.apache.org/jira/browse/HBASE-18512
> Project: HBase
> Issue Type: Bug
> Components: regionserver, security
> Affects Versions: 1.4.0
> Reporter: Pankaj Kumar
> Assignee: Pankaj Kumar
> Priority: Major
> Fix For: 1.4.0, 1.2.7, 1.3.3
>
> Attachments: HBASE-18512-branch-1.patch
>
>
> If HDFS umask (fs.permissions.umask-mode) has limited scope say 077 then
> file/dir permission will not be wider than 700. HDFS client has to set
> permission explicitly if required.
> During SecureBulkLoadEndpoint CP start, RegionServer creates (if not exist)
> the staging directory with the specified permission and later throws
> IllegalStateException if staging directory permission is not set to 711.
> After HBASE-17861, we are setting staging dir permission explicitly only when
> it exist. In case of fresh cluster startup staging dir permission wont be 711
> when umask defined as 077 which cause RS to abort.
> {noformat}
> 2017-07-30 14:26:33,350 | ERROR |
> B.defaultRpcServer.handler=12,queue=2,port=21300 | Region server
> HOSTNAME,PORT,XXXXXXXXX reported a fatal error:
> ABORTING region server HOSTNAME,PORT,XXXXXXXXX: The coprocessor
> org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint threw
> java.lang.IllegalStateException: Staging directory of
> /user/HBase/hbase-staging already exists but permissions aren't set to
> '-rwx--x--x'
> Cause:
> java.lang.IllegalStateException: Staging directory of
> /user/root/hbase-staging already exists but permissions aren't set to
> '-rwx--x--x'
> {noformat}
> We should set permission explicitly to 711 after staging directory creation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
