[
https://issues.apache.org/jira/browse/AMBARI-22074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184016#comment-16184016
]
Hadoop QA commented on AMBARI-22074:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12889303/AMBARI-22074.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/12367//console
This message is automatically generated.
> Confusing AMS collector heap size validation loop
> -------------------------------------------------
>
> Key: AMBARI-22074
> URL: https://issues.apache.org/jira/browse/AMBARI-22074
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-22074.patch
>
>
> Upon clicking Next on Customize Services page of Install Wizard, stack
> advisor reports validation errors.
> It showed a warning on metrics_collector_size, that it should be 8704MB.
> So I hit cancel and set it to 8704MB.
> Upon hitting Next, now it showed a warning saying metrics_collector_size
> should instead be 10880MB.
> So I hit cancel again and set it to 10880MB.
> Upon hitting Next, now it showed a warning saying metrics_collector_size
> should instead be 12544MB.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)