[
https://issues.apache.org/jira/browse/HBASE-18840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16592028#comment-16592028
]
Sean Busbey commented on HBASE-18840:
-------------------------------------
the issue as I understand it is that meta has a superset of the information the
RR cluster wants. the RR cluster wants to know "which of the files in the
storage layer correspond to the table regions that are currently valid for the
table?" and the primary cluster's meta includes e.g. mapping those regions to
active RS instances.
what about relying a consistent snapshot of the table -> region -> hfiles
mapping that gets written out periodically to storage?
> 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)
