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 (Created) (JIRA)" <ji...@apache.org> on 2012/04/04 18:33:27 UTC
[jira] [Created] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
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 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"
--
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
[jira] [Commented] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437399#comment-13437399 ]
stack commented on HBASE-5714:
------------------------------
Patch looks good to me. Nice one Lliang. Jon or Jimmy want to take a look?
> 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
> Attachments: HBASE-5628.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
[jira] [Commented] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437873#comment-13437873 ]
Jonathan Hsieh commented on HBASE-5714:
---------------------------------------
Jie, looks great and thanks for the testing output. I have only a one style nit i'd like your thoughts on:
Can you make the calls to Runtime.getRuntime().exit(xx) happen in main instead of the helper? If we were to write tests, the exit would make it difficult.
> 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
> Attachments: HBASE-5628.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
[jira] [Assigned] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438326#comment-13438326 ]
Hudson commented on HBASE-5714:
-------------------------------
Integrated in HBase-0.92 #509 (See [https://builds.apache.org/job/HBase-0.92/509/])
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
[jira] [Updated] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "liang xie (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
liang xie updated HBASE-5714:
-----------------------------
Attachment: HBASE-5628.patch
A patch for trunk version
> 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
> Attachments: HBASE-5628.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
[jira] [Commented] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438295#comment-13438295 ]
Hudson commented on HBASE-5714:
-------------------------------
Integrated in HBase-0.94 #409 (See [https://builds.apache.org/job/HBase-0.94/409/])
HBASE-5714 Add write permissions check before any hbck run that modifies hdfs (Liang Xie) (Revision 1375228)
Result = SUCCESS
jmhsieh :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
* /hbase/branches/0.94/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
[jira] [Updated] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "liang xie (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
liang xie updated HBASE-5714:
-----------------------------
Attachment: HBASE-5628.patch.v2
Modified per Jon's comments
> 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
> 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
[jira] [Commented] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439529#comment-13439529 ]
Hudson commented on HBASE-5714:
-------------------------------
Integrated in HBase-0.94-security #48 (See [https://builds.apache.org/job/HBase-0.94-security/48/])
HBASE-5714 Add write permissions check before any hbck run that modifies hdfs (Liang Xie) (Revision 1375228)
Result = FAILURE
jmhsieh :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
* /hbase/branches/0.94/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
[jira] [Commented] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "liang xie (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437353#comment-13437353 ]
liang xie commented on HBASE-5714:
----------------------------------
Sorry for no new test-case attached，i'm still a very newbie for HBase project:)
I tested as following steps:
1) run as an under-privileged user on base code, issue this command : "hbase org.apache.hadoop.hbase.util.hbck.OfflineMetaRepair", it failed after several read-only operations
2) apply this patch, rerun , got the fast-fail as expected :
12/08/18 23:37:21 WARN util.HBaseFsck: Got AccessControlException when preCheckPermission
org.apache.hadoop.security.AccessControlException: Permission denied: action=WRITE path=hdfs://10.235.2.121:9000/hbase/-ROOT- user=xiaomi
at org.apache.hadoop.hbase.util.FSUtils.checkAccess(FSUtils.java:1064)
at org.apache.hadoop.hbase.util.HBaseFsck.preCheckPermission(HBaseFsck.java:1184)
at org.apache.hadoop.hbase.util.hbck.OfflineMetaRepair.main(OfflineMetaRepair.java:97)
Current user xiaomi does not have write perms to hdfs://10.235.2.121:9000/hbase/-ROOT-. Please rerun hbck as hdfs user root
> 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
> Attachments: HBASE-5628.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
[jira] [Updated] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hsieh updated HBASE-5714:
----------------------------------
Issue Type: Improvement (was: Sub-task)
Parent: (was: HBASE-5628)
> 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
> 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
[jira] [Updated] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "Jonathan Hsieh (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448314#comment-13448314 ]
Hudson commented on HBASE-5714:
-------------------------------
Integrated in HBase-0.94-security-on-Hadoop-23 #7 (See [https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/7/])
HBASE-5714 Add write permissions check before any hbck run that modifies hdfs (Liang Xie) (Revision 1375228)
Result = FAILURE
jmhsieh :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
* /hbase/branches/0.94/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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hsieh updated HBASE-5714:
----------------------------------
Attachment: hbase-5714-94.patch
hbase-5714-92.patch
hbase-5714-90.patch
Diffs of the backports.
> 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
[jira] [Commented] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438289#comment-13438289 ]
Hudson commented on HBASE-5714:
-------------------------------
Integrated in HBase-TRUNK #3245 (See [https://builds.apache.org/job/HBase-TRUNK/3245/])
HBASE-5714 Add write permissions check before any hbck run that modifies hdfs (Liang Xie) (Revision 1375227)
Result = FAILURE
jmhsieh :
Files :
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
* /hbase/trunk/hbase-server/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
[jira] [Resolved] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hsieh resolved HBASE-5714.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.94.2
0.96.0
0.92.2
0.90.7
Hadoop Flags: Reviewed
> 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
[jira] [Commented] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438315#comment-13438315 ]
Hudson commented on HBASE-5714:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #139 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/139/])
HBASE-5714 Add write permissions check before any hbck run that modifies hdfs (Liang Xie) (Revision 1375227)
Result = FAILURE
jmhsieh :
Files :
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
* /hbase/trunk/hbase-server/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
[jira] [Commented] (HBASE-5714) Add write permissions check before
any hbck run that modifies hdfs.
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438228#comment-13438228 ]
Jonathan Hsieh commented on HBASE-5714:
---------------------------------------
Thanks liang xie! Looks good to me. I'm committing (with minor tweaks to port to 0.94/0.92/0.90). Thanks for the review stack.
> 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
> 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