You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2018/06/08 15:02:00 UTC

[jira] [Commented] (HBASE-20701) too much logging when balancer runs from BaseLoadBalancer

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

Hadoop QA commented on HBASE-20701:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red}  0m  2s{color} | {color:red} Docker failed to build yetus/hbase:dca6535. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-20701 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12927056/HBASE-20701-branch-1.3.patch |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/13160/console |
| Powered by | Apache Yetus 0.7.0   http://yetus.apache.org |


This message was automatically generated.



> too much logging when balancer runs from BaseLoadBalancer
> ---------------------------------------------------------
>
>                 Key: HBASE-20701
>                 URL: https://issues.apache.org/jira/browse/HBASE-20701
>             Project: HBase
>          Issue Type: Improvement
>          Components: Balancer
>            Reporter: Monani Mihir
>            Assignee: Monani Mihir
>            Priority: Trivial
>         Attachments: HBASE-20701-branch-1.3.patch, HBASE-20701-branch-1.4.patch
>
>
> When balancer runs, it tries to find least loaded server with better locality for current region. During this, we make debug level logging for each of those regions. It creates too much amount of logging at debug level , we should move this to trace level logging.
> {code:java}
> int getLeastLoadedTopServerForRegion (int region, int currentServer) {
> ...
>     if (leastLoadedServerIndex != -1) {
>         LOG.debug("Pick the least loaded server " + servers[leastLoadedServerIndex].getHostname()
>         + " with better locality for region " + regions[region]);
>     }
> ...
> }{code}
> This was fixed in branch-2.0 as part of -HBASE-14614-  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)