[
https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440154#comment-13440154
]
Hudson commented on HBASE-5714:
-------------------------------
Integrated in HBase-0.92-security #116 (See
[https://builds.apache.org/job/HBase-0.92-security/116/])
HBASE-5714 Add write permissions check before any hbck run that modifies
hdfs (Liang Xie) (Revision 1375229)
Result = FAILURE
jmhsieh :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
> Add write permissions check before any hbck run that modifies hdfs.
> -------------------------------------------------------------------
>
> Key: HBASE-5714
> URL: https://issues.apache.org/jira/browse/HBASE-5714
> Project: HBase
> Issue Type: Improvement
> Components: hbck
> Affects Versions: 0.90.6, 0.92.2, 0.94.0, 0.96.0
> Reporter: Jonathan Hsieh
> Assignee: liang xie
> Fix For: 0.90.7, 0.92.2, 0.96.0, 0.94.2
>
> Attachments: HBASE-5628.patch, HBASE-5628.patch.v2,
> hbase-5714-90.patch, hbase-5714-92.patch, hbase-5714-94.patch
>
>
> We encoutered a situation where hbck was run by an under-privileged user that
> was unable to write/modify/merge regions due to hdfs perms. Unfortunately,
> this user was alerted of this after several minutes of read-only operations.
> hbck should fail early by having a write perm check and providing actionable
> advice to the hbase admin.
> Maybe something like: "Current user yy does not have write perms to <hbase
> home>. Please run hbck as hdfs user xxx"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
