hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-5714) Add write permissions check before any hbck run that modifies hdfs.
Date Wed, 04 Apr 2012 16:35:23 GMT

     [ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Hsieh updated HBASE-5714:
----------------------------------

    Description: 
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"

  was:
We encoutered a situation where hbase was run by a different user and was unable to write/modify/merge
regions due to hdfs perms.  Unfortunately, this happened 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"

    
> 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: Sub-task
>          Components: hbck
>    Affects Versions: 0.90.6, 0.92.2, 0.94.0, 0.96.0
>            Reporter: Jonathan Hsieh
>
> 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

        

Mime
View raw message