-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-26443 Some BaseLoadBalancer log lines should be at DEBUG level #3838
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
virajjasani
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
ndimiduk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no objections, only a question -- do we currently rely on the presence of these log statements to communicate to the operator that the balancer is running and doing work? Is there instead, maybe a metric or something on the UI that says the balancer is running, when it last ran, how long it's taking in a top style view, anything at all?
|
I don't think balancer activity makes it into the cluster status api. There's a metric for how long the last balancer run took, but that only gets updated when a run finishes. it's up to each balancer implementation to properly set it; the SimpleLoadBalancer doesn't set it. there are other more specific log messages emitted at INFO by the StochasticLoadBalancer about the start of, end of, and performing work. the SimpleLoadBalancer mostly logs at DEBUG and TRACE, with an INFO message only printed at the end of each run. |
|
While not exact |
|
I left the balancer INFO logging as INFO where the message varies from log line to log line and is operationally useful. Only repetitive and uninteresting lines were considered. |
…3838) Signed-off-by: Nick Dimiduk <[email protected]> Signed-off-by: Viraj Jasani <[email protected]> Signed-off-by: Xiaolin Ha <[email protected]>
No description provided.