[
https://issues.apache.org/jira/browse/HBASE-26193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17398346#comment-17398346
]
Zach York commented on HBASE-26193:
-----------------------------------
Yeah I saw that part, it sounds good, definitely a +1. Since the master local
table perists the info in the root directory, it won't be lost even on a new
cluster with existing data.
In that case, we still will run into the problem described in HBASE-24286 for
the meta table because we will:
1. Have a location for the meta existing
2. The meta table won't be open at that server (the server itself is likely
dead)
3. We will wait for it to become open (it never will if there is no SCP)
But obviously that's a different problem than this is trying to solve.
> Do not store meta region location on zookeeper
> ----------------------------------------------
>
> Key: HBASE-26193
> URL: https://issues.apache.org/jira/browse/HBASE-26193
> Project: HBase
> Issue Type: Improvement
> Components: meta, Zookeeper
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
>
> As it breaks one of our design rules
> https://hbase.apache.org/book.html#design.invariants.zk.data
> We used to think hbase should be recovered automatically when all the data on
> zk (except the replication data) are cleared, but obviously, if you clear the
> meta region location, the cluster will be in trouble, and need to use
> operation tools to recover the cluster.
> So here, along with the ConnectionRegistry improvements, we should also
> consider move the meta region location off zookeeper.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
