ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8344) Alerts: Remove Flume Alerts From Host Components
Date Mon, 17 Nov 2014 00:59:33 GMT

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

Hadoop QA commented on AMBARI-8344:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12681813/AMBARI-8344.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 4 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/660//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/660//console

This message is automatically generated.

> Alerts: Remove Flume Alerts From Host Components
> ------------------------------------------------
>
>                 Key: AMBARI-8344
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8344
>             Project: Ambari
>          Issue Type: Task
>          Components: alerts, ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8344.patch
>
>
> With Nagios as the alerting system, Flume alerts needed to be injected into the response
of the status command and manually inserted into the list of cluster alerts. 
> The new alerting system removes the need for this workaround since a single flume script
is now used to check and report on the overall flume state.
> The following areas of code should be removed:
> 1) Remove the alerts from the {{status}} function of {{flume_handler.py}}
> 2) Remove the {{AgentAlert}} from the host components
> 3) Remove the collection of Alerts from the cluster



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

Mime
View raw message