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

Hudson commented on HBASE-20665:
--------------------------------

Results for branch branch-2.0
        [build #400 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/400/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/400//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/400//JDK8_Nightly_Build_Report_(Hadoop2)/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/400//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> "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
>            Assignee: Eric Maynard
>            Priority: Minor
>              Labels: beginner
>             Fix For: 3.0.0, 2.1.0, 1.2.7, 1.3.3, 2.0.1
>
>         Attachments: HBASE-20665.master.001.patch, 
> HBASE-20665.master.001.patch
>
>
> 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)

Reply via email to