[
https://issues.apache.org/jira/browse/HBASE-14793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008907#comment-15008907
]
stack commented on HBASE-14793:
-------------------------------
When G1GC, there is no L2 going on? If there is an L2, the L1 only has index
blocks....and an index block in L1 needs limiting? Must be the former case?
Its good to have a limit regardless.
+1 on patch.
Add release note honey.
> 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.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)
