[
https://issues.apache.org/jira/browse/HBASE-20045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395170#comment-16395170
]
Saad Mufti commented on HBASE-20045:
------------------------------------
Yeah, letting the user define what constitutes "new" would be perfect. As for
running out of bucket cache because eviction of compacted away files happens
later, that is less of a concern for us since we only do major compaction one
region at a time on each region server, but I see your point because some might
be doing overall major compaction all at once and/or might not have enough
bucket cache space. So it makes sense to put in ample warning about these
scenarios.
Look forward to trying any patch.
Cheers.
> When running compaction, cache recent blocks.
> ---------------------------------------------
>
> Key: HBASE-20045
> URL: https://issues.apache.org/jira/browse/HBASE-20045
> Project: HBase
> Issue Type: New Feature
> Components: BlockCache, Compaction
> Affects Versions: 2.0.0-beta-1
> Reporter: Jean-Marc Spaggiari
> Priority: Major
>
> HBase already allows to cache blocks on flush. This is very useful for
> usecases where most queries are against recent data. However, as soon as
> their is a compaction, those blocks are evicted. It will be interesting to
> have a table level parameter to say "When compacting, cache blocks less than
> 24 hours old". That way, when running compaction, all blocks where some data
> are less than 24h hold, will be automatically cached.
>
> Very useful for table design where there is TS in the key but a long history
> (Like a year of sensor data).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
