You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jonathan Hsieh (JIRA)" <ji...@apache.org> on 2012/08/20 23:29:38 UTC
[jira] [Assigned] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hsieh reassigned HBASE-5714:
-------------------------------------
Assignee: liang xie
> 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
> Attachments: HBASE-5628.patch, HBASE-5628.patch.v2
>
>
> 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