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

Hadoop QA commented on AMBARI-11762:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12738207/AMBARI-11762.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:red}-1 core tests{color}.  The test build failed in ambari-server 

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

This message is automatically generated.

> Alerts: alert not triggered when ZKFC is down
> ---------------------------------------------
>
>                 Key: AMBARI-11762
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11762
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11762.patch
>
>
> The HDFS status summary still shows "no alerts" even when the ZKFC is down.  
> Please see screen shots attached. 
> Looking inside the "zookeeper failover controller process", it is monitoring 
> if port 2181 is open. It seems the configuration key is defined is wrong. 



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

Reply via email to