[
https://issues.apache.org/jira/browse/HBASE-25767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-25767:
------------------------------
Description:
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.
was:
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 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
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
>
> 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)
