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

Hadoop QA commented on AMBARI-8215:
-----------------------------------

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

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

This message is automatically generated.

> Flume Service Metrics do not show on Services>Flume page
> --------------------------------------------------------
>
>                 Key: AMBARI-8215
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8215
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Xi Wang
>            Assignee: Xi Wang
>            Priority: Critical
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-8215.patch
>
>
> Repro Steps
> 1. Deploy a 3 node cluster with HDP2.1
> 2. Select all services
> 3. On deployment completion goto Services>Flume
> 4. Notice Flume Service Metrics show error message "There was no data 
> available. Possible reason include inaccessible Ganglia service"
> *Solution:* remove three metrics for Flume : JVM Heap, JVM Runnable Treads 
> and Garbage Collection 



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

Reply via email to