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

Sean Busbey commented on HBASE-18840:
-------------------------------------

Especially if we're looking to move to the master branch, I'd like to figure 
out how this will interact with HBCK2.  [the topic of "how do we bootstrap meta 
in case of catastrophic 
loss"|https://issues.apache.org/jira/browse/HBASE-19121?focusedCommentId=16585114&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16585114]
 is currently active among the folks working on that, but I don't think there's 
a specific JIRA yet.

> Add functionality to refresh meta table at master startup
> ---------------------------------------------------------
>
>                 Key: HBASE-18840
>                 URL: https://issues.apache.org/jira/browse/HBASE-18840
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: HBASE-18477
>            Reporter: Zach York
>            Assignee: Zach York
>            Priority: Major
>         Attachments: HBASE-18840.HBASE-18477.001.patch, 
> HBASE-18840.HBASE-18477.002.patch, HBASE-18840.HBASE-18477.003 (2) (1).patch, 
> HBASE-18840.HBASE-18477.003 (2).patch, HBASE-18840.HBASE-18477.003.patch, 
> HBASE-18840.HBASE-18477.004.patch, HBASE-18840.HBASE-18477.005.patch, 
> HBASE-18840.HBASE-18477.006.patch, HBASE-18840.HBASE-18477.007.patch
>
>
> If a HBase cluster’s hbase:meta table is deleted or a cluster is started with 
> a new meta table, HBase needs the functionality to synchronize it’s metadata 
> from Storage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to