[jira] [Commented] (HBASE-26988) Balancer should reset to default setting for hbase.master.loadbalance.bytable if dynamically reloading configuration

["David Manning (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-26988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529772#comment-17529772 ] 

David Manning commented on HBASE-26988:
---------------------------------------

I randomly didn't notice it when running tests locally, because {{testUpdateBalancerLoadInfo}} also sets it to {{false}} as the last update. So if that test runs in between {{testSloppyTablesLoadBalanceByTable}} and {{testBalanceOfSloppyServers}}, everything is also okay.

> Balancer should reset to default setting for hbase.master.loadbalance.bytable if dynamically reloading configuration
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-26988
>                 URL: https://issues.apache.org/jira/browse/HBASE-26988
>             Project: HBase
>          Issue Type: Bug
>          Components: Balancer
>    Affects Versions: 3.0.0-alpha-1, 2.0.0
>            Reporter: David Manning
>            Assignee: David Manning
>            Priority: Minor
>
> # Set {{hbase.master.loadbalance.bytable}} to {{true}} in {{hbase-site.xml}}
> # Start HMaster
> # Remove {{hbase.master.loadbalance.bytable}} entry in {{hbase-site.xml}}
> # Dynamically reload configuration for hmaster (https://hbase.apache.org/book.html#dyn_config)
> *Expected:* load balancing would no longer happen by table
> *Actual:* load balancing still happens by table
> *Workaround:* leave the entry in {{hbase-site.xml}} but explicitly set to {{false}}
> Note: I see this when running tests added in HBASE-22349, depending on the order of execution of test methods. If {{testSloppyTablesLoadBalanceByTable}} executes before {{testBalanceOfSloppyServers}} there will be a failure. We could apply the workaround to the tests (explicitly set to {{false}}), but it seems better to fix the dynamic reconfiguration behavior.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)