[
https://issues.apache.org/jira/browse/HBASE-18840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16591989#comment-16591989
]
Zach York commented on HBASE-18840:
-----------------------------------
I'm okay with having it interact with HBCK, but this patch only handles the
initial build of the meta table (I still need to consider copying the existing
meta table and removing ip addresses), but the reason I called it refresh meta
is because this will also need to periodically be ran to keep meta in sync on
the RR cluster (add new tables, delete tables, etc). In that case 'refresh'
made more sense.
I'm not sure about what to do in branch-2/master... when I originally developed
this, I hadn't done much with branch-2 (master at the time). Do you think
rebuilding from an existing meta would be easier in this case? We only really
need to be in sync with the other meta table I think. We can still keep some of
this work for hbck2?
> 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)
