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

[jira] [Updated] (HBASE-20701) too much logging when balancer runs

     [ https://issues.apache.org/jira/browse/HBASE-20701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Monani Mihir updated HBASE-20701:
---------------------------------
    Description: 
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

    if (leastLoadedServerIndex != -1) {
        LOG.debug("Pick the least loaded server " + servers[leastLoadedServerIndex].getHostname()
        + " with better locality for region " + regions[region]);
    }{code}

> too much logging when balancer runs
> -----------------------------------
>
>                 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
>
> 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
>     if (leastLoadedServerIndex != -1) {
>         LOG.debug("Pick the least loaded server " + servers[leastLoadedServerIndex].getHostname()
>         + " with better locality for region " + regions[region]);
>     }{code}



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