[
https://issues.apache.org/jira/browse/HBASE-26988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Manning updated HBASE-26988:
----------------------------------
Description:
# 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 1*: The steps may only work if the config value is not in
{{hbase-default.xml}} so it may be an unlikely scenario.
*Note 2*: 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. Regardless, I will
propose test fixes in HBASE-26989.
was:
# 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.
> 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 1*: The steps may only work if the config value is not in
> {{hbase-default.xml}} so it may be an unlikely scenario.
> *Note 2*: 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. Regardless, I will propose test
> fixes in HBASE-26989.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
