hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15513) hbase.hregion.memstore.chunkpool.maxsize is 0.0 by default
Date Tue, 19 Apr 2016 04:17:25 GMT

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

Anoop Sam John commented on HBASE-15513:
----------------------------------------

It is like fixed at the init time. Say we have 10GB max heap size and 40% as memstore size
(ie. 4GB) and if hbase.hregion.memstore.chunkpool.maxsize = 1, then 4 GB is reserved for MSLAB
pool.  So it is not changing with memstore size.
Ya when the auto tuner changes the memstore size (up or down), this chunk size wont get changed
too.. May be that is some thing wrong and to be corrected?

> 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