You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2014/11/05 00:45:35 UTC

[jira] [Commented] (AMBARI-8143) Alerts: NameNode Health HA Alert Check

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

Hadoop QA commented on AMBARI-8143:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12679301/AMBARI-8143.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 7 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:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

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

This message is automatically generated.

> Alerts: NameNode Health HA Alert Check
> --------------------------------------
>
>                 Key: AMBARI-8143
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8143
>             Project: Ambari
>          Issue Type: Task
>          Components: alerts, ambari-agent, ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8143.patch
>
>
> The NameNode HA health check alert must be rewritten as a SCRIPT based alert since it requires advanced logic and knowledge of all NameNode states to make the correct alert state determination.
> This will also involve extending alert definitions to include the ability to ignore the host reporting the alert, essentially collapsing all alert instances into a single entry regardless of originating host.



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