[
https://issues.apache.org/jira/browse/AMBARI-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141375#comment-16141375
]
Yao Lei edited comment on AMBARI-18574 at 8/25/17 8:40 AM:
-----------------------------------------------------------
Hi [~sumitmohanty] ,
Thanks for your review. Please see updated patch [^AMBARI-18574_2.patch] .
hbase.hregion.memstore.chunkpool.maxsize will be added as part of a upgrade to
stack HDP 2.6.
Testes in a real cluster. It works.
was (Author: yaolei):
Hi [~sumitmohanty] ,
Thanks for your review. Please see updated patch [^AMBARI-18574_2.patch] .
hbase.hregion.memstore.chunkpool.maxsize will be added as part of a upgrade to
stack 2.6.
Testes in a real cluster. It works.
> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---------------------------------------------------
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-18574_2.patch, AMBARI-18574.patch
>
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
> final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
