[jira] [Commented] (HBASE-6223) Document hbck improvements: HBASE-6173, HBASE-5360
[ https://issues.apache.org/jira/browse/HBASE-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485298#comment-13485298 ] Hudson commented on HBASE-6223: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #240 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/240/]) HBASE-6223 Document hbck improvements: HBASE-6173, HBASE-5360 (Revision 1402650) Result = FAILURE jxiang : Files : * /hbase/trunk/src/docbkx/book.xml > Document hbck improvements: HBASE-6173, HBASE-5360 > --- > > Key: HBASE-6223 > URL: https://issues.apache.org/jira/browse/HBASE-6223 > Project: HBase > Issue Type: Task > Components: documentation, hbck >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: trunk-6223.patch, trunk-6223_v2.patch, > trunk-6223_v3.patch > > > We had a couple hbck improvements recently: HBASE-6173 and HBASE-5360. > We should document them. Especially, for HBASE-5360, it's something > one normally doesn't do. -- 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] [Commented] (HBASE-6223) Document hbck improvements: HBASE-6173, HBASE-5360
[ https://issues.apache.org/jira/browse/HBASE-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485224#comment-13485224 ] Hudson commented on HBASE-6223: --- Integrated in HBase-TRUNK #3489 (See [https://builds.apache.org/job/HBase-TRUNK/3489/]) HBASE-6223 Document hbck improvements: HBASE-6173, HBASE-5360 (Revision 1402650) Result = FAILURE jxiang : Files : * /hbase/trunk/src/docbkx/book.xml > Document hbck improvements: HBASE-6173, HBASE-5360 > --- > > Key: HBASE-6223 > URL: https://issues.apache.org/jira/browse/HBASE-6223 > Project: HBase > Issue Type: Task > Components: documentation, hbck >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.96.0 > > Attachments: trunk-6223.patch, trunk-6223_v2.patch, > trunk-6223_v3.patch > > > We had a couple hbck improvements recently: HBASE-6173 and HBASE-5360. > We should document them. Especially, for HBASE-5360, it's something > one normally doesn't do. -- 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] [Commented] (HBASE-6223) Document hbck improvements: HBASE-6173, HBASE-5360
[ https://issues.apache.org/jira/browse/HBASE-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485093#comment-13485093 ] stack commented on HBASE-6223: -- +1 Reads much better. > Document hbck improvements: HBASE-6173, HBASE-5360 > --- > > Key: HBASE-6223 > URL: https://issues.apache.org/jira/browse/HBASE-6223 > Project: HBase > Issue Type: Task > Components: documentation, hbck >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Attachments: trunk-6223.patch, trunk-6223_v2.patch, > trunk-6223_v3.patch > > > We had a couple hbck improvements recently: HBASE-6173 and HBASE-5360. > We should document them. Especially, for HBASE-5360, it's something > one normally doesn't do. -- 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] [Commented] (HBASE-6223) Document hbck improvements: HBASE-6173, HBASE-5360
[
https://issues.apache.org/jira/browse/HBASE-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485089#comment-13485089
]
Hadoop QA commented on HBASE-6223:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12550986/trunk-6223_v3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated
85 warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 3 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/3156//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3156//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3156//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3156//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3156//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3156//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3156//console
This message is automatically generated.
> Document hbck improvements: HBASE-6173, HBASE-5360
> ---
>
> Key: HBASE-6223
> URL: https://issues.apache.org/jira/browse/HBASE-6223
> Project: HBase
> Issue Type: Task
> Components: documentation, hbck
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
> Attachments: trunk-6223.patch, trunk-6223_v2.patch,
> trunk-6223_v3.patch
>
>
> We had a couple hbck improvements recently: HBASE-6173 and HBASE-5360.
> We should document them. Especially, for HBASE-5360, it's something
> one normally doesn't do.
--
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] [Commented] (HBASE-6223) Document hbck improvements: HBASE-6173, HBASE-5360
[ https://issues.apache.org/jira/browse/HBASE-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484707#comment-13484707 ] stack commented on HBASE-6223: -- +1 on commit. On commit add in a 'the' between 'in' and 'right'. Should that be 'or not deployed' (add 'or') and 'so you can' -- add a 'so'? Maybe break up the big sentence. Its hard to pass. Good on you Jimmy. +Once a region is split, the offline parent will be cleaned up automatically. Sometimes, daughter regions +are split again before their parents are cleaned up. HBase can clean up parents in right order. However, +if there is a lingering offline split parent, i.e. it's in META, in HDFS, not deployed, HBase can't +clean it up, you can use the -fixSplitParents option to reset the parent in META to be +online and not split so that hbck can merge it with other regions with options to fix +overlapping regions. This option should not normally be used, and it is not in -fixAll. > Document hbck improvements: HBASE-6173, HBASE-5360 > --- > > Key: HBASE-6223 > URL: https://issues.apache.org/jira/browse/HBASE-6223 > Project: HBase > Issue Type: Task > Components: documentation, hbck >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Attachments: trunk-6223.patch, trunk-6223_v2.patch > > > We had a couple hbck improvements recently: HBASE-6173 and HBASE-5360. > We should document them. Especially, for HBASE-5360, it's something > one normally doesn't do. -- 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] [Commented] (HBASE-6223) Document hbck improvements: HBASE-6173, HBASE-5360
[
https://issues.apache.org/jira/browse/HBASE-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484604#comment-13484604
]
Hadoop QA commented on HBASE-6223:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12550888/trunk-6223_v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated
85 warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 3 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/3153//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3153//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3153//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3153//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3153//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3153//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3153//console
This message is automatically generated.
> Document hbck improvements: HBASE-6173, HBASE-5360
> ---
>
> Key: HBASE-6223
> URL: https://issues.apache.org/jira/browse/HBASE-6223
> Project: HBase
> Issue Type: Task
> Components: documentation, hbck
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
> Attachments: trunk-6223.patch, trunk-6223_v2.patch
>
>
> We had a couple hbck improvements recently: HBASE-6173 and HBASE-5360.
> We should document them. Especially, for HBASE-5360, it's something
> one normally doesn't do.
--
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] [Commented] (HBASE-6223) Document hbck improvements: HBASE-6173, HBASE-5360
[
https://issues.apache.org/jira/browse/HBASE-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484529#comment-13484529
]
Hadoop QA commented on HBASE-6223:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12550864/trunk-6223.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated
85 warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 3 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/3150//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3150//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3150//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3150//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3150//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/3150//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3150//console
This message is automatically generated.
> Document hbck improvements: HBASE-6173, HBASE-5360
> ---
>
> Key: HBASE-6223
> URL: https://issues.apache.org/jira/browse/HBASE-6223
> Project: HBase
> Issue Type: Task
> Components: documentation, hbck
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
> Attachments: trunk-6223.patch
>
>
> We had a couple hbck improvements recently: HBASE-6173 and HBASE-5360.
> We should document them. Especially, for HBASE-5360, it's something
> one normally doesn't do.
--
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] [Commented] (HBASE-6223) Document hbck improvements: HBASE-6173, HBASE-5360
[ https://issues.apache.org/jira/browse/HBASE-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409222#comment-13409222 ] Jonathan Hsieh commented on HBASE-6223: --- Motivation for HBASE-5360: We encountered a situation where a parent was marked off-line in meta, where data still existed in HDFS, and where we actually wanted to restore the data that was in the FS. I believe the old behavior was to skip these regions with the assumption that daughter regions were good. In this particular case, the daughter regions were not -- I believe one of the two were missing, and we wanted an option to "revive" the parent region. This would likely cause an overlap with the surviving daughter region -- but we already had mechanisms to handle that (-fixHdfsOverlaps). The -fixSplitParents option is should not normally be used (it is not part of -fixAll). Motivation for HBASE-6173: We ran into a situation withe cluster that had a large number of regions (~20k, for 50 nodes or so). The file system operations for loading this data, even though it happened in parallel took a very long time. This addition allowed us just to reduced the time for a report by only focusing on a particular table. > Document hbck improvements: HBASE-6173, HBASE-5360 > --- > > Key: HBASE-6223 > URL: https://issues.apache.org/jira/browse/HBASE-6223 > Project: HBase > Issue Type: Task > Components: documentation, hbck >Reporter: Jimmy Xiang > > We had a couple hbck improvements recently: HBASE-6173 and HBASE-5360. > We should document them. Especially, for HBASE-5360, it's something > one normally doesn't do. -- 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
