[
https://issues.apache.org/jira/browse/HBASE-30408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18129740#comment-18129740
]
Tak-Lon (Stephen) Wu edited comment on HBASE-30408 at 10/21/26 4:26 PM:
------------------------------------------------------------------------
Recently one of our colleagues was proposing to use Ratis (or similar protocol)
to handle the leases and master election, would that be a candidate for this
effort as well? I commented that would require a major refactoring (obviously).
was (Author: taklwu):
Recently one of our colleagues were proposing to use Ratis (or similar
protocol) to handle the leases and master election, would that be a candidate
for this effort as well, I commented that would require a major refactoring
(obviously).
> Reduce zookeeper dependencies in HBase
> --------------------------------------
>
> Key: HBASE-30408
> URL: https://issues.apache.org/jira/browse/HBASE-30408
> Project: HBase
> Issue Type: Umbrella
> Components: Zookeeper
> Reporter: Duo Zhang
> Priority: Major
>
> We have been working hard in the past to reduce the zookeeper dependencies in
> HBase, and finally we have made sure that for core features, we do not store
> persistent data on zookeeper, only use zk to manage the rs leases and for
> active master election.
> But recently, when investigating the code(with AI asistant), I found that
> there are still lots of heavy usage of zookeeper, like the in ACL, we mirror
> all the ACL data on zk and use zk to sync the acl permission data, it leads
> to great pressure on zk when the cluster is large(see HBASE-24211).
> And in quota implementation, we store the throttle flag on zookeeper, this is
> a persistent data, which will loss data when recreating a cluster based on
> only fs data.
> So this issue is an umbrella issue for tracking all these things and also
> tell our developers to not adding more pressures on zk in the future.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
