[
https://issues.apache.org/jira/browse/HBASE-14942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045777#comment-15045777
]
Elliott Clark commented on HBASE-14942:
---------------------------------------
Yes this is off heap, and probably not the largest issue. And I don't know for
sure that it will be *the* culprit. However when running G1 we're seeing way
too many things end up in the old gen that shouldn't be. So I'm trying to find
all things that are keeping objects alive in the name of not fragmenting the
heap. Any of those things make life much worse on a recent garbage collector.
> Allow turning off BoundedByteBufferPool
> ---------------------------------------
>
> Key: HBASE-14942
> URL: https://issues.apache.org/jira/browse/HBASE-14942
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0, 1.2.0, 1.3.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: HBASE-14942.patch
>
>
> The G1 does a great job of compacting, there's no reason to use the
> BoundedByteBufferPool when the JVM can it for us. So we should allow turning
> this off for people who are running new jvm's where the G1 is working well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
