[ https://issues.apache.org/jira/browse/HBASE-25767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320967#comment-17320967 ]
Hudson commented on HBASE-25767: -------------------------------- Results for branch master [build #263 on builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/263/]: (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/263/General_20Nightly_20Build_20Report/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/263/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/] (/) {color:green}+1 jdk11 hadoop3 checks{color} -- For more information [see jdk11 report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/263/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} > CandidateGenerator.getRandomIterationOrder is too slow on large cluster > ----------------------------------------------------------------------- > > Key: HBASE-25767 > URL: https://issues.apache.org/jira/browse/HBASE-25767 > Project: HBase > Issue Type: Improvement > Components: Balancer, Performance > Reporter: Duo Zhang > Assignee: Duo Zhang > Priority: Major > Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3, 2.3.6 > > > Similar to HBASE-25759, it is just used to test whether we should skip > calculation, but in production masterServices will never be null. > ========== > Update, change the title of this issue for removing > CandidateGenerator.getRandomIterationOrder as it is too slow which causes the > CandidateGenerator.getRandomIterationOrder to fail when we remove the > masterServices field in LocalityBasedCandidateGenerator. As this is the most > important change in this issue so change the title of this issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)