[ https://issues.apache.org/jira/browse/HDFS-11832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017724#comment-16017724 ]
Chen Liang commented on HDFS-11832: ----------------------------------- Thanks [~10075197] for the followup. But just similar to [~ajisakaa] mentioned, I think the variable gets evaluated regardless of the log level. There is [this|http://stackoverflow.com/questions/8444266/even-with-slf4j-should-you-guard-your-logging] discussion. > Switch leftover logs to slf4j format in BlockManager.java > --------------------------------------------------------- > > Key: HDFS-11832 > URL: https://issues.apache.org/jira/browse/HDFS-11832 > Project: Hadoop HDFS > Issue Type: Improvement > Components: namenode > Affects Versions: 2.7.0, 2.8.0, 3.0.0-alpha1 > Reporter: Hui Xu > Assignee: Chen Liang > Priority: Minor > Attachments: HDFS-11832.001.patch, HDFS-11832.002.patch, > HDFS-11832.003.patch, HDFS-11832.004.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > HDFS-7706 Switch BlockManager logging to use slf4j. But the logging formats > were not modified appropriately. For example: > if (LOG.isDebugEnabled()) { > LOG.debug("blocks = " + java.util.Arrays.asList(blocks)); > } > These codes should be modified to: > LOG.debug("blocks = {}", java.util.Arrays.asList(blocks)); -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org