[
https://issues.apache.org/jira/browse/HBASE-26193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397846#comment-17397846
]
Duo Zhang commented on HBASE-26193:
-----------------------------------
I think the simplest way is to just use the approach in HBASE-24388, to store
the meta region location in master local region, but still publish it to
zookeeper and region servers will still get the location from zookeeper.
If we want to completely remove zookeeper here, then there will be several
candidates, and it will effect how we implement splittable meta in the future.
So let me put up a design doc first.
> 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)
