[ https://issues.apache.org/jira/browse/AMBARI-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139867#comment-16139867 ]
Hadoop QA commented on AMBARI-18574: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12883477/AMBARI-18574.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 core tests{color}. The patch passed unit tests in ambari-server. Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12055//console This message is automatically generated. > 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.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)