[
https://issues.apache.org/jira/browse/HBASE-28364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817888#comment-17817888
]
Wellington Chevreuil commented on HBASE-28364:
----------------------------------------------
{quote}Do you think it’s an actually problem we should track down?
{quote}
Yeah, I had verified that already, it's not actual an issue. When we are
reading blocks sequentially, we don't have how to know what's the actual next
block type, so we pass null to the blockType param
[here|https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/HFileReaderImpl.java#L758].
So it's expected, that logging should be removed. I'm gonna revert it.
> Warn: Cache key had block type null, but was found in L1 cache
> --------------------------------------------------------------
>
> Key: HBASE-28364
> URL: https://issues.apache.org/jira/browse/HBASE-28364
> Project: HBase
> Issue Type: Bug
> Reporter: Bryan Beaudreault
> Priority: Major
>
> I'm ITBLL testing branch-2.6 and am seeing lots of these warns. This is new
> to me. I would expect a warn to be on the rare side or be indicative of a
> problem, but unclear from the code.
> cc [~wchevreuil]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
