[
https://issues.apache.org/jira/browse/HBASE-14793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15015242#comment-15015242
]
Anoop Sam John commented on HBASE-14793:
----------------------------------------
Sorry for being late here and asking after commit. Some Qs
When the size of the block is more than this defined size and we have L1 and L2
cache, we can make sure at least we will cache it in L2? Data blocks will go
to L2 block only by default unless we marked it for L1 cache. In that case also
(marked for L1 cache) we can allow it to be cached to L2 ?
In case of a setup of L1 and L2 cache with combinedMode=false (ie. L2 is set as
victim handler for L1) we will just avoid caching the bigger blocks as the
caching there 1st happens to L1. Here also we can directly put that block to L2
cache only?
> Allow limiting size of block into L1 block cache.
> -------------------------------------------------
>
> Key: HBASE-14793
> URL: https://issues.apache.org/jira/browse/HBASE-14793
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.2.0, 1.1.2
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: HBASE-14793-v1.patch, HBASE-14793-v3.patch,
> HBASE-14793-v4.patch, HBASE-14793-v5.patch, HBASE-14793-v6.patch,
> HBASE-14793-v7.patch, HBASE-14793.patch
>
>
> G1GC does really badly with long lived large objects. Lets allow limiting the
> size of a block that can be kept in the block cache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
