[jira] [Resolved] (HBASE-25767) CandidateGenerator.getRandomIterationOrder is too slow on large cluster

["Duo Zhang (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-25767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duo Zhang resolved HBASE-25767.
-------------------------------
    Resolution: Fixed

Pushed to branch-2+.

Thanks [~niuyulin] and [~Ddupg] for reviewing.

As this is something like a 'behavior change', so here I do not cherry-pick the patch back to branch-2.4 and branch-2.3.

Ping [~apurtell], [~ndimiduk], [~huaxiangsun]. Feel free to reopen for backporting if you think it is worth.

Thanks.

> 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
>
>
> 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)