[
https://issues.apache.org/jira/browse/HBASE-18840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299219#comment-16299219
]
Zach York commented on HBASE-18840:
-----------------------------------
[~stack] I agree that it would be better to get this information from
hbase:meta if this existed, but this patch is more for the case where the
hbase:meta doesn't exist so that wouldn't work.
I know that there are some gaps with this functionality (listed below), but
this is best effort functionality (usually used when storefiles and regions are
stable):
1) Won't handle in process splits
2) Anything not flushed to storefiles will be missed.
Also we currently have users utilizing this functionality for their read
replica clusters. I think long term we might need to think of a better solution
(especially if we want to remove the regioninfo files), but currently this is
working.
> 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
> Attachments: HBASE-18840.HBASE-18477.001.patch,
> HBASE-18840.HBASE-18477.002.patch, HBASE-18840.HBASE-18477.003 (2).patch,
> HBASE-18840.HBASE-18477.003.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
(v6.4.14#64029)
