[
https://issues.apache.org/jira/browse/HBASE-23116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16944880#comment-16944880
]
Bharath Vissapragada commented on HBASE-23116:
----------------------------------------------
I see what you are saying. It is annoying for an RM if things keep getting
piled up in the last minute. Anyway, I've subscribed to the dev list and I'll
keep an eye on things going forward.
Coming to the back port, like you said, it appears there are some non-trivial
changes to ClusterStatus. I don't have much context of those, so I've created a
slightly pared down patch that passes the tests. Here it is if you can take a
look. Thanks. https://github.com/apache/hbase/pull/689
> LoadBalancer should log table name when balancing per table
> -----------------------------------------------------------
>
> Key: HBASE-23116
> URL: https://issues.apache.org/jira/browse/HBASE-23116
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 1.4.10, 2.2.1, 2.1.6
> Reporter: Andrew Kyle Purtell
> Assignee: Bharath Vissapragada
> Priority: Minor
> Fix For: 3.0.0, 1.5.0, 2.3.0, 1.4.11, 2.2.2, 1.3.7, 2.1.8
>
>
> The load balancer logs lines like these:
> {noformat}
> 2019-10-02 23:18:47,664 INFO [46493_ChoreService_6]
> balancer.StochasticLoadBalancer - Skipping load balancing because balanced
> cluster; total cost is 46.68964334022376, sum multiplier is 1087.0 min cost
> which need balance is 0.05
> {noformat}
> When balancing per table it would be useful if the table name was also
> printed in the log line.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
