[
https://issues.apache.org/jira/browse/AMBARI-17695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378839#comment-15378839
]
Hadoop QA commented on AMBARI-17695:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12818043/AMBARI-17695-3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-metrics/ambari-metrics-timelineservice ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7853//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7853//console
This message is automatically generated.
> AMS: Split point calculation not optimal for large clusters.
> ------------------------------------------------------------
>
> Key: AMBARI-17695
> URL: https://issues.apache.org/jira/browse/AMBARI-17695
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.4.0
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Labels: ambari-metrics
> Fix For: 2.4.0
>
> Attachments: AMBARI-17695-3.patch
>
>
> Use hbase.regionserver.global.memstore.upperLimit instead of lowerLimit for
> available memory for split points calculation. Change default region counts
> for METRIC_RECORD and METRIC_AGGREGATE to 2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
