[ https://issues.apache.org/jira/browse/HBASE-20701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522999#comment-16522999 ]
Hudson commented on HBASE-20701: -------------------------------- SUCCESS: Integrated in Jenkins build HBase-1.3-IT #424 (See [https://builds.apache.org/job/HBase-1.3-IT/424/]) HBASE-20701 too much logging when balancer runs from BaseLoadBalancer (apurtell: rev 3a5d00398df14a10dcb1a95df0c6c68a2bafd8e9) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/BaseLoadBalancer.java > 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 > Fix For: 1.5.0, 1.3.3, 1.4.6 > > Attachments: HBASE-20701-branch-1.3.patch, > HBASE-20701-branch-1.3.patch, HBASE-20701-branch-1.3.patch, > HBASE-20701-branch-1.4.patch, HBASE-20701-branch-1.4.patch, > HBASE-20701.branch-1.001.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)