[HBASE-23350] Make compaction files cacheonWrite configurable based on threshold

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha-1, 2.3.0
• Component/s: Compaction

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.

• Assignee: Abhinaba Sarkar
• Reporter: ramkrishna.s.vasudevan
• Created: 29/Nov/19 04:14
• Updated: 11/Mar/20 11:26
• Resolved: 04/Feb/20 04:33

Description

As per comment from chenxu 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.

Issue Links

• links to: GitHub Pull Request #1074
• links to: PR