[
https://issues.apache.org/jira/browse/HBASE-24408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531866#comment-17531866
]
ruanhui edited comment on HBASE-24408 at 5/5/22 5:28 PM:
---------------------------------------------------------
hi all
Since we have MasterLocalRegion now, I think we can put some data that was
previously on zookeeper in the MasterLocalRegion, like the balancer switch,
mergeOrsplit switch, region normalizer switch. This is also a attempt to make
hbase less dependent on zk. Do you think this is worthwhile work?
was (Author: frostruan):
hi all
Since we have MasterLocalRegion now, I think we can put some data that was
previously on zookeeper in the MasterLocalRegion, like the balancer switch,
mergeOrsplit switch, region normalizer switch, rsgroup infos, these data is
only accessed by master. This is also a attempt to make hbase less dependent on
zk. Do you think this is worthwhile work?
> Introduce a general 'local region' to store data on master
> ----------------------------------------------------------
>
> Key: HBASE-24408
> URL: https://issues.apache.org/jira/browse/HBASE-24408
> Project: HBase
> Issue Type: Task
> Components: master
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Blocker
> Fix For: 3.0.0-alpha-1, 2.3.0
>
>
> We already have a local region to store the procedure data and when
> implementing HBASE-11288, splittable meta, we are thinking of also storing
> the data for root table in a local region.
> Now in the patch for HBASE-24388, we introduced another local region to store
> the data for root table, but maybe it is better to store the procedure data
> and root table together in a single region(with different families).
> And this should be done before 2.3.0, to prevent shipping the procedure store
> region out in a release. Set it a blocker for 2.3.0.
> Patch will be available soon.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
