[
https://issues.apache.org/jira/browse/HBASE-25007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193990#comment-17193990
]
Duo Zhang commented on HBASE-25007:
-----------------------------------
{quote}
I don't follow. HBCKSCP doesn't do assign of meta
{quote}
This is exactly the problem. In HBCKSCP we introduced a way to fix the 'unknown
server' problem, but the same trick can not be used to fix meta, then how do we
fix the cluster if meta is on an 'unknown server'?
Or, if we have a way to make meta up, without using the trick in HBCKSCP, where
we scan meta table to search for 'unknown servers', which means we can bring
meta up with normal SCP, then why not use SCP to bring other regions up? What
is the value of HBCKSCP?
{quote}
Yes, TestHBCKSCP, could indeed be 'artificial' (The things that HBCKSCP
addresses cannot be addressed by master restart... ). Disable, file an issue
and assign me to fix (w/ a suggestion on how better to test if you have one)?
{quote}
Could you please explain more on why the things can not be addressed by master
restart? As we will read meta again when restarting master?
Thanks.
> Make HBCK2 work for 'root table'
> --------------------------------
>
> Key: HBASE-25007
> URL: https://issues.apache.org/jira/browse/HBASE-25007
> Project: HBase
> Issue Type: Sub-task
> Components: hbck2
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
>
> We will also scan catalog table and fix them in HBCK2, we should add support
> for root too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
