We already have a connection to zookeeper at region server side, and
we already watched a lot of things, so watching one more znode does
not add too much pressure to zk.
And I've been implementing a framework to replicate meta location
without zookeeper, this could reduce the pressure on zookeeper
Are you referring to meta region location(s) cache? If so, yes we will have
more network chatter accessing those znode(s) whenever meta (replicas) move
around (what happens in split-meta is still under discussion as you
probably are already following, but it is likely that we will still use ZK
as t
Clara Xiong created HBASE-26207:
---
Summary: config hbase.regions.slop is used for stochastic load
balancer.
Key: HBASE-26207
URL: https://issues.apache.org/jira/browse/HBASE-26207
Project: HBase
I recall that there was a concern about data freshness, that the masters
were all tracking the necessary state and all of them would always be
up-to-date. Region servers were not already in this business, and doing so
would put undue burden on ZooKeeper.
Perhaps I miss-remember, or the discussion
[
https://issues.apache.org/jira/browse/HBASE-24337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-24337.
---
Fix Version/s: 2.5.0
Hadoop Flags: Reviewed
Resolution: Fixed
Backported to bran
[
https://issues.apache.org/jira/browse/HBASE-26187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wellington Chevreuil resolved HBASE-26187.
--
Resolution: Fixed
Amended UTs to check for split proc completion before moving
Duo Zhang created HBASE-26206:
-
Summary: Remove masterless related code in HRegionServer
Key: HBASE-26206
URL: https://issues.apache.org/jira/browse/HBASE-26206
Project: HBase
Issue Type: Task
[
https://issues.apache.org/jira/browse/HBASE-26087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaolin Ha resolved HBASE-26087.
Fix Version/s: 2.3.7
2.4.6
3.0.0-alpha-2
2
