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

ASF GitHub Bot commented on HADOOP-18717:
-----------------------------------------

steveloughran commented on code in PR #6445:
URL: https://github.com/apache/hadoop/pull/6445#discussion_r1452694820


##########
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/compress/CodecPool.java:
##########
@@ -150,7 +150,9 @@ public static Compressor getCompressor(CompressionCodec 
codec, Configuration con
     Compressor compressor = borrow(compressorPool, codec.getCompressorType());
     if (compressor == null) {
       compressor = codec.createCompressor();
-      LOG.info("Got brand-new compressor ["+codec.getDefaultExtension()+"]");
+      if(LOG.isDebugEnabled()) {

Review Comment:
   no need to wrap, just use {} so that the toString() call on 
codec.getDefaultExtension is only called once. yes, I know about the old code, 
but that's old code





> Move CodecPool getCompressor/getDecompressor logs to DEBUG
> ----------------------------------------------------------
>
>                 Key: HADOOP-18717
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18717
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: common
>    Affects Versions: 3.3.6
>            Reporter: Claire McGinty
>            Priority: Trivial
>              Labels: pull-request-available
>
> The "Got brand new compressor|decompressor" logs in CodecPool[0] can be quite 
> noisy when reading thousands of blocks and aren't that illuminating for the 
> end user. I'd like to propose moving them from log.info to log.debug if 
> there's no objection.
>  
> [0] 
> https://github.com/apache/hadoop/blob/b737869e01fe3334b948a38fe3835e48873bf3a6/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/compress/CodecPool.java#L149-L195



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to