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 (Commented) (JIRA)" <ji...@apache.org> on 2012/04/03 22:22:23 UTC
[jira] [Commented] (HBASE-5599) The hbck tool can not fix the six
scenarios, it is NO_VERSION_FILE, NOT_IN_META_OR_DEPLOYED, NOT_IN_META,
SHOULD_NOT_BE_DEPLOYED, FIRST_REGION_STARTKEY_NOT_EMPTY,
HOLE_IN_REGION_CHAIN.
[ https://issues.apache.org/jira/browse/HBASE-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245688#comment-13245688 ]
Jonathan Hsieh commented on HBASE-5599:
---------------------------------------
Thanks for the updates, the new patch looks pretty good. A few things to follow up on before commit:
- If adding a test case is hard, let's file new issue to "add HBCK test case for SHOULD_NOT_BE_DEPLOYED case".
- Change the text here to be "Try to fix missing hbase.version file in hdfs."
{code}
System.err.println(" -fixVersionFile Try to fix the hbase.version missing.");
{code}
- I noticed the Merge.java changes are still present in the newer patch -- is that intended? It don't seem necessary or related to this issue.
This should be good to commit for 0.90, if you address these issues.
Could you provide an updated version for trunk?
Thanks!
> The hbck tool can not fix the six scenarios, it is NO_VERSION_FILE, NOT_IN_META_OR_DEPLOYED, NOT_IN_META, SHOULD_NOT_BE_DEPLOYED, FIRST_REGION_STARTKEY_NOT_EMPTY, HOLE_IN_REGION_CHAIN.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-5599
> URL: https://issues.apache.org/jira/browse/HBASE-5599
> Project: HBase
> Issue Type: New Feature
> Components: hbck
> Affects Versions: 0.90.6
> Reporter: fulin wang
> Assignee: fulin wang
> Fix For: 0.90.6
>
> Attachments: hbase-5599-0.90.patch, hbase-5599-0.90_v2.patch, hbase-5599-0.90_v3.patch, hbase-5599-0.90_v5.patch, hbase-5599-0.90_v6.patch, hbase-5599-0.92_v5.patch, hbase-5599-0.94_v5.patch, hbase-5599-trunk_v5.patch
>
>
> The hbck tool can not fix the six scenarios.
> 1. Version file does not exist in root dir.
> Fix: I try to create a version file by 'FSUtils.setVersion' method.
>
> 2. [REGIONNAME][KEY] on HDFS, but not listed in META or deployed on any region server.
> Fix: I get region info form the hdfs file, this region info write to '.META.' table.
>
> 3. [REGIONNAME][KEY] not in META, but deployed on [SERVERNAME]
> Fix: I get region info form the hdfs file, this region info write to '.META.' table.
>
> 4. [REGIONNAME] should not be deployed according to META, but is deployed on [SERVERNAME]
> Fix: Close this region.
>
> 5. First region should start with an empty key. You need to create a new region and regioninfo in HDFS to plug the hole.
> Fix: The region info is not in hdfs and .META., so it create a empty region for this error.
> 6. There is a hole in the region chain between [KEY] and [KEY]. You need to create a new regioninfo and region dir in hdfs to plug the hole.
> Fix: The region info is not in hdfs and .META., so it create a empty region for this hole.
>
--
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