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

Xiao Zhang updated HBASE-24234:
-------------------------------
    Description: 
In the validateChecksum method of the ChecksumUtil class, still use LOG.info 
after judging LOG.isTraceEnabled.

eg:

if (LOG.isTraceEnabled()) {
 LOG.info("dataLength=" + buffer.capacity()
     + ", sizeWithHeader=" + onDiskDataSizeWithHeader
     + ", checksumType=" + cktype.getName()
     + ", file=" + pathName
     + ", offset=" + offset
     + ", headerSize=" + hdrSize
     + ", bytesPerChecksum=" + bytesPerChecksum);
}

  was:
In the validateChecksum method of the ChecksumUtil class, still use LOG.info 
after judging LOG.isTraceEnabled.

eg:

if (LOG.*isTraceEnabled*()) {
 LOG.*info*("dataLength=" + buffer.capacity()
 + ", sizeWithHeader=" + onDiskDataSizeWithHeader
 + ", checksumType=" + cktype.getName()
 + ", file=" + pathName
 + ", offset=" + offset
 + ", headerSize=" + hdrSize
 + ", bytesPerChecksum=" + bytesPerChecksum);
}


> ChecksumUtil class validateChecksum method log level does not match
> -------------------------------------------------------------------
>
>                 Key: HBASE-24234
>                 URL: https://issues.apache.org/jira/browse/HBASE-24234
>             Project: HBase
>          Issue Type: Bug
>          Components: HFile
>    Affects Versions: 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.2.4
>            Reporter: Xiao Zhang
>            Assignee: Xiao Zhang
>            Priority: Minor
>
> In the validateChecksum method of the ChecksumUtil class, still use LOG.info 
> after judging LOG.isTraceEnabled.
> eg:
> if (LOG.isTraceEnabled()) {
>  LOG.info("dataLength=" + buffer.capacity()
>      + ", sizeWithHeader=" + onDiskDataSizeWithHeader
>      + ", checksumType=" + cktype.getName()
>      + ", file=" + pathName
>      + ", offset=" + offset
>      + ", headerSize=" + hdrSize
>      + ", bytesPerChecksum=" + bytesPerChecksum);
> }



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to