You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Jeremy Carroll (JIRA)" <ji...@apache.org> on 2016/08/31 15:29:22 UTC

[jira] [Commented] (HBASE-15513) hbase.hregion.memstore.chunkpool.maxsize is 0.0 by default

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

Jeremy Carroll commented on HBASE-15513:
----------------------------------------

Looking for guidance on this as well. We are still running CMS due to the fact that we could not get G1GC latency under ~100ms (max). So is the advice to set to 1, and disable heap auto tuning?

> 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)