[
https://issues.apache.org/jira/browse/HBASE-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644842#comment-15644842
]
Anoop Sam John commented on HBASE-15513:
----------------------------------------
I mean , now we make MSLAB pool ON by default and 100% memstore size is the max
size. So if there are writes we will keep adding MSLAB chunks to pool. This
will be permanent in the pool. Later when there are not many writes also we
will occupy 40% of the memory with SLAB chunks (def value am taking).. The
Heap tuner, if ON, will tune the memstore size down and that will even do
release of some of the unwanted chunks. THat is why I was saying we need to
turn heap tuner also ON by def now. There is a jira for that already. Make
sense?
> 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-addendum.patch, 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)
