[ 
https://issues.apache.org/jira/browse/HBASE-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122344#comment-13122344
 ] 

Jonathan Hsieh commented on HBASE-4377:
---------------------------------------

In the 0.90 branch, after deleting meta and restarting the # of tables present 
is 0.
In trunk and 0.92 branch, after deleting meta and restart the # of tables 
present is 1.  

This actually does make sense because HBASE-451 changed the behavior of HMaster 
-- in 0.90 (pre-HBASE-451) it HConnectionManager.listTables() loads table info 
on the client side via a meta scan.  Post HBASE-451, table data from  
HConnectionManager.listTables() comes from the files system and is cached by 
the HMaster, and ignores the meta table.
                
> [hbck] Offline rebuild .META. from fs data only.
> ------------------------------------------------
>
>                 Key: HBASE-4377
>                 URL: https://issues.apache.org/jira/browse/HBASE-4377
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Jonathan Hsieh
>            Assignee: Jonathan Hsieh
>         Attachments: 
> 0001-HBASE-4377-hbck-Offline-rebuild-.META.-from-fs-data-.patch, 
> hbase-4377-trunk.v2.patch
>
>
> In a worst case situation, it may be helpful to have an offline .META. 
> rebuilder that just looks at the file system's .regioninfos and rebuilds meta 
> from scratch.  Users could move bad regions out until there is a clean 
> rebuild.  
> It would likely fill in region split holes.  Follow on work could given 
> options to merge or select regions that overlap, or do online rebuilds.

--
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

        

Reply via email to