You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2021/10/26 13:44:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17434374#comment-17434374 ]
Hudson commented on HBASE-26327:
--------------------------------
Results for branch master
[build #423 on builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/423/]: (x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/423/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/423/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/423/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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
>
> 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.3.4#803005)