hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Masatake Iwasaki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9618) Fix mismatch between log level and guard in BlockManager#computeRecoveryWorkForBlocks
Date Wed, 06 Jan 2016 09:48:39 GMT

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

Masatake Iwasaki commented on HDFS-9618:
----------------------------------------

{code}
    if (blockLog.isInfoEnabled()) {
      // log which blocks have been scheduled for replication
      for(BlockRecoveryWork rw : recovWork){
        DatanodeStorageInfo[] targets = rw.getTargets();
        if (targets != null && targets.length != 0) {
          StringBuilder targetList = new StringBuilder("datanode(s)");
          for (DatanodeStorageInfo target : targets) {
            targetList.append(' ');
            targetList.append(target.getDatanodeDescriptor());
          }
          blockLog.debug("BLOCK* ask {} to replicate {} to {}", rw.getSrcNodes(),
              rw.getBlock(), targetList);
        }
      }
    }
{code}


> Fix mismatch between log level and guard in BlockManager#computeRecoveryWorkForBlocks
> -------------------------------------------------------------------------------------
>
>                 Key: HDFS-9618
>                 URL: https://issues.apache.org/jira/browse/HDFS-9618
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Masatake Iwasaki
>            Assignee: Masatake Iwasaki
>            Priority: Minor
>
> Debug log message is constructed when {{Logger#isInfoEnabled}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message