[
https://issues.apache.org/jira/browse/AMBARI-13037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735969#comment-14735969
]
Hadoop QA commented on AMBARI-13037:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12754695/AMBARI-13037_1.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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-metrics/ambari-metrics-timelineservice ambari-server:
org.apache.ambari.server.controller.internal.RequestResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3741//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3741//console
This message is automatically generated.
> AMS - stack advisor should recommend topology smarts alongwith optimistic
> settings
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-13037
> URL: https://issues.apache.org/jira/browse/AMBARI-13037
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics, ambari-server
> Affects Versions: 2.0.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.1.2
>
> Attachments: AMBARI-13037_1.patch
>
>
> Goals:
> Metrics Collector is placed on a less busy master
> AMS HBase root dir is set to a separate mount if available, WARN user if the
> default mount point say "/" is selected when some other partition is
> available.
> Set hbase.tmpdir to separate mount or "/" (different from rootdir) if such an
> option is available.
> Fine tune memory settings for clusters under 100 nodes but that have resource
> avaialble, we see that sometimes 50 node settings are too conservative for a
> 40 node cluster but they are fine for a 10 node.
> Tune the metrics collection frequency (This is experimental item, I am not
> sure this will help in reducing load)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
