You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2013/03/08 18:18:13 UTC
[jira] [Resolved] (HBASE-8042) Offline Meta Repair no longer points
to the correct location
[ https://issues.apache.org/jira/browse/HBASE-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-8042.
--------------------------
Resolution: Fixed
Fix Version/s: 0.95.0
Assignee: Kevin Odell
Committed to trunk. Will show next time we push website. Thanks Kevin.
> Offline Meta Repair no longer points to the correct location
> ------------------------------------------------------------
>
> Key: HBASE-8042
> URL: https://issues.apache.org/jira/browse/HBASE-8042
> Project: HBase
> Issue Type: Bug
> Components: documentation
> Reporter: Kevin Odell
> Assignee: Kevin Odell
> Fix For: 0.95.0
>
>
> B.4.3. Special case: Root and META are corrupt.
> The most drastic corruption scenario is the case where the ROOT or META is corrupted and HBase will not start. In this case you can use the OfflineMetaRepair tool create new ROOT and META regions and tables. This tool assumes that HBase is offline. It then marches through the existing HBase home directory, loads as much information from region metadata files (.regioninfo files) as possible from the file system. If the region metadata has proper table integrity, it sidelines the original root and meta table directories, and builds new ones with pointers to the region directories and their data.
> $ ./bin/hbase org.apache.hadoop.hbase.util.OfflineMetaRepair
> The path should be org.apache.hadoop.hbase.util.hbck.OfflineMetaRepair
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira