hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Rodionov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15513) hbase.hregion.memstore.chunkpool.maxsize is 0.0 by default
Date Fri, 02 Sep 2016 14:54:20 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15458739#comment-15458739
] 

Vladimir Rodionov commented on HBASE-15513:
-------------------------------------------

{quote}
The reason why chunk pool is better with G1GC is as Anoop stated but that is for lower heap
sizes. For higher heap sizes may be it is not needed to be ON by default? So am not very sure
whether we should always enable this chunkpool. When we use offheap MSLAB then yes, it has
to be ON, so that we avoid offheap memory fragmentation.
{quote}



> hbase.hregion.memstore.chunkpool.maxsize is 0.0 by default
> ----------------------------------------------------------
>
>                 Key: HBASE-15513
>                 URL: https://issues.apache.org/jira/browse/HBASE-15513
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0
>            Reporter: Vladimir Rodionov
>            Assignee: Vladimir Rodionov
>             Fix For: 2.0.0
>
>         Attachments: HBASE-15513-v1.patch
>
>
> That results in excessive MemStoreLAB chunk allocations because we can not reuse them.
Not sure, why it has been disabled, by default. May be the code has not been tested well?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message