You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Eric Maynard (JIRA)" <ji...@apache.org> on 2018/06/06 16:35:00 UTC
[jira] [Commented] (HBASE-20665) "Already cached block XXX" message
should be DEBUG
[ https://issues.apache.org/jira/browse/HBASE-20665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503556#comment-16503556 ]
Eric Maynard commented on HBASE-20665:
--------------------------------------
I've opened a PR here: https://github.com/apache/hbase/pull/77
> "Already cached block XXX" message should be DEBUG
> --------------------------------------------------
>
> Key: HBASE-20665
> URL: https://issues.apache.org/jira/browse/HBASE-20665
> Project: HBase
> Issue Type: Task
> Components: BlockCache
> Affects Versions: 1.2.0, 2.0.0
> Reporter: Sean Busbey
> Priority: Minor
> Labels: beginner
> Fix For: 3.0.0, 2.1.0, 1.5.0, 1.2.7, 1.3.3, 1.4.5
>
>
> Testing a local cluster that relies on the LruBlockCache for a scan-heavy workload and I'm getting a bunch of log entries at WARN
> {code}
> 2018-05-30 12:28:47,192 WARN org.apache.hadoop.hbase.io.hfile.LruBlockCache: Cached an already cached block: df01f5bf6a244f6bb1a626b927377fff_54780812 cb:df01f5bf6a244f6bb1a626b927377fff_54780812. This is harmless and can happen in rare cases (see HBASE-8547)
> {code}
> As the log message notes (and the code confirms) this is a harmless result of contention for getting a block into the CHM. the message should be at DEBUG.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)