You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2017/08/05 02:47:00 UTC
[jira] [Updated] (AMBARI-18574) Set
hbase.hregion.memstore.chunkpool.maxsize to 1.0
[ https://issues.apache.org/jira/browse/AMBARI-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated AMBARI-18574:
----------------------------
Description:
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
was:
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
> 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
>
> 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)