[
https://issues.apache.org/jira/browse/HBASE-26193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429496#comment-17429496
]
Tak-Lon (Stephen) Wu edited comment on HBASE-26193 at 10/15/21, 10:09 PM:
--------------------------------------------------------------------------
in HBASE-24833, [~anoop.hbase] asked if it could be merged to branch-2.4 and I
get here, I felt like HBASE-26193 could be merged as well. I did cherry-pick
onto branch-2.4 and the logic seems fine just the behavior change with the
MasterRegion (ran the changed unit test).
but before I open the PR, do you guys here have any concern?
was (Author: taklwu):
in HBASE-24833, [~anoop.hbase] asked if it could be merged to branch-2.4 and I
get here, I felt like HBASE-26193 could be merged as well and did cherry-pick
onto branch-2.4, but before I open the PR, do you guys here have any concern?
> Do not store meta region location as permanent state 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
> Fix For: 2.5.0, 3.0.0-alpha-2
>
>
> 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)
