[
https://issues.apache.org/jira/browse/HBASE-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235191#comment-13235191
]
[email protected] commented on HBASE-5128:
------------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4280/
-----------------------------------------------------------
(Updated 2012-03-21 23:24:13.538416)
Review request for hbase, Todd Lipcon, Ted Yu, and Lars Hofhansl.
Changes
-------
Updated from Ted and Stack's reviews.
Highlights:
- usage and actual command line params renamed and updated.
Summary
-------
This version is similar to the 0.90.x version posted a few months back, but has
a few new features and some minor differences.
1) No trackHTD method needed since we can read from the file system.
2) Added safeguards to prevent mega merges, and to isolate repairs to
particular tables.
3) Fixed comparator in HRegionInfo
4) Fixed TestRegionObserverInterface so that it doesn't rely on bug in
HRegionInfo comparator.
I'll backport to 0.94/0.92 (which should be very similar) and update the 0.90
versions after this patch has mostly cleared.
This version is not perfect (there are definitely cases not covered) but it
think it is worth trying to get this in so that future reviews are more
manageable.
This addresses bug HBASE-5128.
https://issues.apache.org/jira/browse/HBASE-5128
Diffs (updated)
-----
src/main/java/org/apache/hadoop/hbase/ipc/HMasterInterface.java 3c635d4
src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java d47ef10
src/main/java/org/apache/hadoop/hbase/master/HMaster.java cd1755f
src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java c0aaf65
src/main/java/org/apache/hadoop/hbase/util/HBaseFsckRepair.java 5916d9c
src/main/java/org/apache/hadoop/hbase/util/hbck/OfflineMetaRepair.java
d57bb6b
src/main/java/org/apache/hadoop/hbase/util/hbck/TableIntegrityErrorHandler.java
PRE-CREATION
src/main/java/org/apache/hadoop/hbase/util/hbck/TableIntegrityErrorHandlerImpl.java
PRE-CREATION
src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java d9a2a02
src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java 937781d
src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsckComparator.java
0599da1
src/test/java/org/apache/hadoop/hbase/util/hbck/HbckTestingUtil.java dbb97f8
src/test/java/org/apache/hadoop/hbase/util/hbck/TestOfflineMetaRebuildBase.java
2b4cac8
src/test/java/org/apache/hadoop/hbase/util/hbck/TestOfflineMetaRebuildHole.java
ebbeead
src/test/java/org/apache/hadoop/hbase/util/hbck/TestOfflineMetaRebuildOverlap.java
b175548
Diff: https://reviews.apache.org/r/4280/diff
Testing
-------
Unit tests cover many many situations and pass. Most "live" testing has been
done on 0.90.x versions. Many improvements and features added from experience.
Not much testing live on the trunk versions.
Thanks,
jmhsieh
> [uber hbck] Enable hbck to automatically repair table integrity problems as
> well as region consistency problems while online.
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-5128
> URL: https://issues.apache.org/jira/browse/HBASE-5128
> Project: HBase
> Issue Type: New Feature
> Components: hbck
> Affects Versions: 0.90.5, 0.92.0, 0.94.0, 0.96.0
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Attachments: hbase-5128-trunk-v2.patch, hbase-5128-trunk.patch
>
>
> The current (0.90.5, 0.92.0rc2) versions of hbck detects most of region
> consistency and table integrity invariant violations. However with '-fix' it
> can only automatically repair region consistency cases having to do with
> deployment problems. This updated version should be able to handle all cases
> (including a new orphan regiondir case). When complete will likely deprecate
> the OfflineMetaRepair tool and subsume several open META-hole related issue.
> Here's the approach (from the comment of at the top of the new version of the
> file).
> {code}
> /**
> * HBaseFsck (hbck) is a tool for checking and repairing region consistency
> and
> * table integrity.
> *
> * Region consistency checks verify that META, region deployment on
> * region servers and the state of data in HDFS (.regioninfo files) all are in
> * accordance.
> *
> * Table integrity checks verify that that all possible row keys can resolve
> to
> * exactly one region of a table. This means there are no individual
> degenerate
> * or backwards regions; no holes between regions; and that there no
> overlapping
> * regions.
> *
> * The general repair strategy works in these steps.
> * 1) Repair Table Integrity on HDFS. (merge or fabricate regions)
> * 2) Repair Region Consistency with META and assignments
> *
> * For table integrity repairs, the tables their region directories are
> scanned
> * for .regioninfo files. Each table's integrity is then verified. If there
> * are any orphan regions (regions with no .regioninfo files), or holes, new
> * regions are fabricated. Backwards regions are sidelined as well as empty
> * degenerate (endkey==startkey) regions. If there are any overlapping
> regions,
> * a new region is created and all data is merged into the new region.
> *
> * Table integrity repairs deal solely with HDFS and can be done offline --
> the
> * hbase region servers or master do not need to be running. These phase can
> be
> * use to completely reconstruct the META table in an offline fashion.
> *
> * Region consistency requires three conditions -- 1) valid .regioninfo file
> * present in an hdfs region dir, 2) valid row with .regioninfo data in META,
> * and 3) a region is deployed only at the regionserver that is was assigned
> to.
> *
> * Region consistency requires hbck to contact the HBase master and region
> * servers, so the connect() must first be called successfully. Much of the
> * region consistency information is transient and less risky to repair.
> */
> {code}
--
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
