[HBASE-5599] [hbck] handle NO_VERSION_FILE and SHOULD_NOT_BE_DEPLOYED inconsistencies

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.90.6
• Fix Version/s: 0.94.0, 0.95.0
• Component/s: hbck
• Hadoop Flags: Reviewed
• Assignee: fulin wang
• Reporter: fulin wang
• Due: 19/Mar/12
• Created: 19/Mar/12 02:58
• Updated: 26/Feb/13 08:12
• Resolved: 11/Apr/12 17:21

Description

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.

Issue Links

• is related to: HBASE-5128 [uber hbck] Online automated repair of table integrity and region consistency problems