[jira] [Commented] (AMBARI-14769) Stack advisor AMS memory validation seems wrong

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-14769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112372#comment-15112372 ] 

Hadoop QA commented on AMBARI-14769:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12783747/AMBARI-14769.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 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-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/5028//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5028//console

This message is automatically generated.

> Stack advisor AMS memory validation seems wrong
> -----------------------------------------------
>
>                 Key: AMBARI-14769
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14769
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.2.1
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>            Priority: Critical
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-14769.patch
>
>
> PROBLEM
> Stack advisor recommendations for AMS heap sizes are unreasonable. 
> BUG
> Stack advisor uses fixed values of 1024M for metrics collector and HBase heapsize for estimating required memory for the components in the host.
> FIX
> Use the user entered values for metrics collector heapsize and AMS HBase heapsize to calculate the required memory on the host.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)