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/03/20 06:21:54 UTC
[jira] [Commented] (HBASE-5599) The hbkc 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=13233220#comment-13233220 ]
Jonathan Hsieh commented on HBASE-5599:
---------------------------------------
@ram @fulin
I'm working on getting HBASE-5128 into trunk/0.94/0.92/0.90. I'm focusing on trunk first (0.94/0.92 should fall out) and changes from the trunk versions (max merge and specific table safegurds) should make it into the 0.90 version.
I believe NOT_IN_META_OR_DEPLOYED, NOT_IN_META, HOLE_IN_REGION_CHAIN are handled by the HBASE-5128. I believe the others are shortcomings.
Fulin, give me a few days to get HBASE-5128 in -- I'm testing a prerequisite of it currently (HBASE-5589).
> The hbkc 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
> Fix For: 0.90.6
>
> Attachments: hbase-5599-0.90.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