[
https://issues.apache.org/jira/browse/HBASE-26443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell updated HBASE-26443:
----------------------------------------
Description:
These are printed per chore run, per host:
{noformat}
[00]2021-11-10 22:07:32,984 INFO [master/ip-172-31-58-47:8100.Chore.1]
balancer.BaseLoadBalancer: Start Generate Balance plan for cluster.
{noformat}
{noformat}
[00]2021-11-10 22:07:32,998 INFO [master/ip-172-31-58-47:8100.Chore.1]
balancer.BaseLoadBalancer: server <N> is on rack <R>
{noformat}
....
One log line per server. On a large cluster, this is a lot of unnecessary
logging.
The 'Start Generate Balance plan for cluster.' log line should be at DEBUG.
The 'server <N> is on rack <R>' log line arguably should be at TRACE. It is not
interesting unless you are debugging the balancer.
While we are in here, this should also be logged at DEBUG level:
{noformat}
[00]2021-11-10 22:14:33,005 INFO [master/ip-172-31-58-47:8100.Chore.1]
master.HMaster: Balancer is going into sleep until next period in 60000ms
{noformat}
was:
These are printed per chore run, per host:
[00]2021-11-10 22:07:32,984 INFO [master/ip-172-31-58-47:8100.Chore.1]
balancer.BaseLoadBalancer: Start Generate Balance plan for cluster.
[00]2021-11-10 22:07:32,998 INFO [master/ip-172-31-58-47:8100.Chore.1]
balancer.BaseLoadBalancer: server <N> is on rack <R>
....
One log line per server. On a large cluster, this is a lot of unnecessary
logging.
The 'Start Generate Balance plan for cluster.' log line should be at DEBUG.
The 'server <N> is on rack <R>' log line arguably should be at TRACE. It is not
interesting unless you are debugging the balancer.
> Some BaseLoadBalancer log lines should be at DEBUG level
> --------------------------------------------------------
>
> Key: HBASE-26443
> URL: https://issues.apache.org/jira/browse/HBASE-26443
> Project: HBase
> Issue Type: Task
> Components: logging, Operability
> Affects Versions: 2.4.9
> Reporter: Andrew Kyle Purtell
> Assignee: Andrew Kyle Purtell
> Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.9
>
>
> These are printed per chore run, per host:
> {noformat}
> [00]2021-11-10 22:07:32,984 INFO [master/ip-172-31-58-47:8100.Chore.1]
> balancer.BaseLoadBalancer: Start Generate Balance plan for cluster.
> {noformat}
> {noformat}
> [00]2021-11-10 22:07:32,998 INFO [master/ip-172-31-58-47:8100.Chore.1]
> balancer.BaseLoadBalancer: server <N> is on rack <R>
> {noformat}
> ....
> One log line per server. On a large cluster, this is a lot of unnecessary
> logging.
> The 'Start Generate Balance plan for cluster.' log line should be at DEBUG.
> The 'server <N> is on rack <R>' log line arguably should be at TRACE. It is
> not interesting unless you are debugging the balancer.
> While we are in here, this should also be logged at DEBUG level:
> {noformat}
> [00]2021-11-10 22:14:33,005 INFO [master/ip-172-31-58-47:8100.Chore.1]
> master.HMaster: Balancer is going into sleep until next period in 60000ms
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
