[
https://issues.apache.org/jira/browse/HBASE-23350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinaba Sarkar updated HBASE-23350:
------------------------------------
Release Note:
This JIRA adds a new configuration -
`hbase.rs.cachecompactedblocksonwrite.threshold`. This configuration is the
maximum total size (in bytes) of the compacted files below which the
configuration `hbase.rs.cachecompactedblocksonwrite` is honoured. If the total
size of the compacted fies exceeds this threshold, even when
`hbase.rs.cachecompactedblocksonwrite` is enabled, the data blocks are not
cached. Caching index and bloom blocks is not affected by this configuration
(user configuration is always honoured).
Default value of this configuration is Long.MAX_VALUE. This means whatever the
total size of the compacted files, it wil be cached.
> Make compaction files cacheonWrite configurable based on threshold
> ------------------------------------------------------------------
>
> Key: HBASE-23350
> URL: https://issues.apache.org/jira/browse/HBASE-23350
> Project: HBase
> Issue Type: Sub-task
> Components: Compaction
> Reporter: ramkrishna.s.vasudevan
> Assignee: Abhinaba Sarkar
> Priority: Major
> Fix For: 3.0.0
>
>
> As per comment from [~javaman_chen] in the parent JIRA
> https://issues.apache.org/jira/browse/HBASE-23066?focusedCommentId=16937361&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16937361
> This is to introduce a config to identify if the resulting compacted file's
> blocks should be added to the cache - while writing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
