[
https://issues.apache.org/jira/browse/HBASE-18840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591927#comment-16591927
]
stack commented on HBASE-18840:
-------------------------------
Back (after seeing [~busbey] comment). You want to recreate hbase:meta table
[~zyork] where there is none?
A few of us chatted recently about how to do fixup if all of the master wal
procedure logs were removed or went corrupt -- the link Sean dropped above.
You want something more radical (rebuild of hbase:meta). How to do it in
branch-2/master branch? On the one hand we want to undo reliance on a
particular fs layout -- our current layout may not make sense for fs's other
than HDFS -- so pulling schema and .regioninfos from a particular location may
not always work.
That said, to be robust, supporting rebuild from bread crumbs post catastrophe
would be a good-to-have. Suggest hbck2 would be the tool to do it manipulating
master in a new "maintenance mode".
> 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)
