[
https://issues.apache.org/jira/browse/HBASE-4094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh resolved HBASE-4094.
---
Resolution: Duplicate
Release Note: (was: The hbck tool(org.apache.hadoop.hbase.util.HBaseFsck)
can check and repair consistency problem.
some error just be checked but not supply the way to repair, I plan to fix it
by other tool(close_region...)or by new method.
First, list it and discuss that is it right?
Part A:check meta info
1.errors.reportError(ERROR_CODE.NULL_ROOT_REGION,Root Region or some of its
attributes are null.);
-- after delete the root table,execute hbck tool to check
but the tool run error. how to reproduce this error?
2.errors.reportError(ERROR_CODE.NO_META_REGION, .META. is not found on any
region.);
--after delete the meta table,execute hbck tool to check but the
tool run error. how to reproduce this error?
3.errors.reportError(ERROR_CODE.MULTI_META_REGION, .META. is found on more
than one region.);
-the logic:scan the root table to get META table
regioninfo,if META table's regions is more than one,throw the error.
HBase allow META table has more than
one region,is it?
Part B:check Consistency
4.ERROR_CODE.NOT_IN_META_HDFSclose it from regionserver.
5.ERROR_CODE.NOT_IN_META_OR_DEPLOYEDdo nothing,maybe it will be used to
fix the chain hole in part C.
6.ERROR_CODE.NOT_IN_METAclose it from regionserver.
7.ERROR_CODE.NOT_IN_HDFS_OR_DEPLOYEDdelete it from META table,it will make
a chain hole, when check chain integrity(in part C) to fix it.
8.ERROR_CODE.NOT_IN_HDFSdelete it from META table and close it from
regionserver,when check chain integrity(in part C) to fix it.
9.ERROR_CODE.NOT_DEPLOYEDassign it.
10.ERROR_CODE.SHOULD_NOT_BE_DEPLOYEDdelete if from META table and close it
from regionserver.
11.ERROR_CODE.MULTI_DEPLOYED---close all from regionservers,and reassign it.
12.ERROR_CODE.SERVER_DOES_NOT_MATCH_METAclose all from regionservers,and
reassign it.
Part C:check chain Integrity
13.ERROR_CODE.FIRST_REGION_STARTKEY_NOT_EMPTY---treat it as a hole
problem(ERROR_CODE.HOLE_IN_REGION_CHAIN).
14.ERROR_CODE.LAST_REGION_ENDKEY_NOT_EMPTY(new add)---treat it as a hole
problem(ERROR_CODE.HOLE_IN_REGION_CHAIN).
15.ERROR_CODE.REGION_CYCLEshut down cluster and merge two region by merge
tool(org.apache.hadoop.hbase.util.Merge)
16.ERROR_CODE.DUPE_STARTKEYS---shut down cluster and merge two region by merge
tool(org.apache.hadoop.hbase.util.Merge)
17.ERROR_CODE.OVERLAP_IN_REGION_CHAIN---shut down cluster and merge two region
by merge tool(org.apache.hadoop.hbase.util.Merge)
18.ERROR_CODE.HOLE_IN_REGION_CHAIN---write a new method to fix it,the logic
is:for recover the data,collect the regionfo from regionserver and hdfs.if a
region's key range is overlaping with the hole range,put it in META table and
assign it,maybe it will create overlapping problem,we can fix it by merge
tool.if no region be collected,create a new region by the hole key range to fix
it.)
Changed to duplicate.
improve hbck tool to fix more hbase problem
---
Key: HBASE-4094
URL: https://issues.apache.org/jira/browse/HBASE-4094
Project: HBase
Issue Type: New Feature
Components: master
Affects Versions: 0.90.3
Reporter: feng xu
Fix For: 0.90.7
Attachments: HbaseFsck_TableChain.patch
Original Estimate: 12h
Remaining Estimate: 12h
--
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
