[jira] [Comment Edited] (HBASE-24441) CacheConfig details logged at Store open is not really useful

["Lijin Bin (Jira)" <ji...@apache.org>]

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

Lijin Bin edited comment on HBASE-24441 at 6/9/20, 6:21 AM:
------------------------------------------------------------

Push to 2.3+, [~songxincun] thanks for the contribution.


was (Author: aoxiang):
Push to 2.3+

> CacheConfig details logged at Store open is not really useful
> -------------------------------------------------------------
>
>                 Key: HBASE-24441
>                 URL: https://issues.apache.org/jira/browse/HBASE-24441
>             Project: HBase
>          Issue Type: Improvement
>          Components: logging, regionserver
>    Affects Versions: 3.0.0-alpha-1
>            Reporter: Anoop Sam John
>            Assignee: song XinCun
>            Priority: Minor
>
> CacheConfig constructor is logging 'this' object at INFO level. This log comes during Store open(As CacheConfig instance for that store is created). As the log is at CacheConfig only, we don't get to know this is for which region:store. So not really useful log.
> {code}
> blockCache=org.apache.hadoop.hbase.io.hfile.CombinedBlockCache@7bc02941, cacheDataOnRead=true, cacheDataOnWrite=true, cacheIndexesOnWrite=false, cacheBloomsOnWrite=false, cacheEvictOnClose=false, cacheDataCompressed=false, prefetchOnOpen=false
> {code}
> Also during every compaction also this logs keeps coming. This is because during compaction we create new CacheConfig based on the HStore level CacheConfig object.  We can avoid this log with every compaction happening.



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