hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6223) Document hbck improvements: HBASE-6173, HBASE-5360
Date Fri, 26 Oct 2012 04:55:12 GMT

    [ 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 <code>-fixSplitParents</code> 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 <code>-fixAll</code>.
                
> 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

Mime
View raw message