You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2021/11/11 02:02:00 UTC
[jira] [Resolved] (HBASE-26327) Replicas cohosted on a rack
shouldn't keep triggering Balancer
[ https://issues.apache.org/jira/browse/HBASE-26327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang resolved HBASE-26327.
-------------------------------
Fix Version/s: 2.5.0
3.0.0-alpha-2
2.4.9
Hadoop Flags: Reviewed
Resolution: Fixed
> Replicas cohosted on a rack shouldn't keep triggering Balancer
> --------------------------------------------------------------
>
> Key: HBASE-26327
> URL: https://issues.apache.org/jira/browse/HBASE-26327
> Project: HBase
> Issue Type: Sub-task
> Components: Balancer
> Reporter: Clara Xiong
> Assignee: Clara Xiong
> Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.9
>
>
> Currently, Balancer has a shortcut check for cohosted replicas of the same region/host/rack and will keep triggering balancer if it is non-zero.
> With the trending of kube and cloud solution for HBase, operators don't have full control of the topology or are not even aware of the topology. There are cases that it is not possible to satisfy or requires sacrificing other constraints such as region count balancing on RS. We want to keep there per RS/host check for availability of regions, especially for meta region. We haven't heard problem with rack so far. The cost functions will still be considered during balancing.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)