[
https://issues.apache.org/jira/browse/HBASE-26193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-26193:
------------------------------
Fix Version/s: 3.0.0-alpha-2
2.5.0
Hadoop Flags: Reviewed
Release Note:
Introduce a new 'info' family in master local region for storing the location
of meta regions.
We will still mirror the location of meta regions to ZooKeeper, for backwards
compatibility. But now you can also clean the meta location znodes(usually
prefixed with 'meta-region-server') on ZooKeeper without mess up the cluster
state. You can get a clean restart of the cluster, and after restarting, we
will mirror the location of meta regions to ZooKeeper again.
> 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)
