[
https://issues.apache.org/jira/browse/HBASE-18840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172466#comment-16172466
]
Zach York commented on HBASE-18840:
-----------------------------------
[~stack] Hmm, I'm not familiar with that I guess. Are the region infos not
updated on region merge/splits? That's all we really need to get is the splits
in the key space for a table in order to know the number of regions and assign
regions on a cluster. Otherwise, if you start a cluster with a new meta table
(in the case it was deleted or for Read-Replica clusters - though perhaps we
could do that differently), you will not be able to access any of the data.
This is kind of interesting because a 'list' command will return the correct
list of tables, but when you try to do a scan on a table, it will fail since
the table/regions aren't in the meta table and no RS are serving it.
Regardless, I'll put up the patch with the initial approach and we can discuss.
> 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
> Reporter: Zach York
> Assignee: Zach York
>
> 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
(v6.4.14#64029)
