This is an automated email from the ASF dual-hosted git repository.

apurtell pushed a commit to branch branch-2.3
in repository https://gitbox.apache.org/repos/asf/hbase.git


The following commit(s) were added to refs/heads/branch-2.3 by this push:
     new 08f9169  HBASE-25642 Fix or stop warning about already cached block 
(#3638)
08f9169 is described below

commit 08f91690e75d941bdeba7537b6729d31f72c78e4
Author: Andrew Purtell <[email protected]>
AuthorDate: Tue Aug 31 09:25:31 2021 -0700

    HBASE-25642 Fix or stop warning about already cached block (#3638)
    
    Our logs have as a fairly common occurrence: 2021-03-05 22:24:31,034 WARN
    [StoreFileOpener-foo-1] hfile.BlockCacheUtil: Caching an already cached
    block: blah.bub. This is harmless and can happen in rare cases (see 
HBASE-8547)
    
    Because it is harmless, log at DEBUG level, not WARN.
    
    Signed-off-by: Baiqiang Zhao <[email protected]>
    Signed-off-by: Duo Zhang <[email protected]>
    Signed-off-by: Viraj Jasani <[email protected]>
    Reviewed-by: Rushabh Shah <[email protected]>
---
 .../src/main/java/org/apache/hadoop/hbase/io/hfile/BlockCacheUtil.java  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/BlockCacheUtil.java
 
b/hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/BlockCacheUtil.java
index 2672992..c2cf821 100644
--- 
a/hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/BlockCacheUtil.java
+++ 
b/hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/BlockCacheUtil.java
@@ -244,7 +244,7 @@ public class BlockCacheUtil {
             + "nextBlockOnDiskSize set, Keeping cached block.");
         return false;
       } else {
-        LOG.warn("Caching an already cached block: {}. This is harmless and 
can happen in rare "
+        LOG.debug("Caching an already cached block: {}. This is harmless and 
can happen in rare "
             + "cases (see HBASE-8547)",
           cacheKey);
         return false;

Reply via email to