[jira] [Updated] (HBASE-29071) StochasticLoadBalancer candidate generators should use a Map, rather than ordinal based indexing

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

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

Duo Zhang updated HBASE-29071:
------------------------------
    Fix Version/s: 2.6.2
                       (was: 2.6.3)

> StochasticLoadBalancer candidate generators should use a Map, rather than ordinal based indexing
> ------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-29071
>                 URL: https://issues.apache.org/jira/browse/HBASE-29071
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 2.6.1
>            Reporter: Ray Mattingly
>            Assignee: Ray Mattingly
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0-alpha-1, 2.7.0, 3.0.0-beta-2, 2.6.2
>
>
> The StochasticLoadBalancer maintains an enum of generator types, and then using the ordinal of that enum to order a list of candidate generators. This approach is needlessly fragile, and I think we should refactor it to use a Map instead.
> As a bonus, using a map could unlock the ability to support pluggable candidate generation if we wanted. I think that could be a nice way to offer robust balancer customization, without requiring that people write complex cost functions or an entire balancer implementation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)