[jira] [Commented] (AMBARI-9781) Aggregate Alerts Are Not Calculated When Receiving the Initial Alert Instance

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

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

Hadoop QA commented on AMBARI-9781:
-----------------------------------

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

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

This message is automatically generated.

> Aggregate Alerts Are Not Calculated When Receiving the Initial Alert Instance
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-9781
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9781
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9781.patch
>
>
> Configured NameNode HA. Build #435, 3-node cluster
> The Percent JournalNodes Available alert has no instances. But the JournalNode process alert has three instances as expected.
> This happens when the alert has not run yet and the component is brought online. The first time the alert runs, it records an OK, which is technically not a state change (since there was no prior state). Because no state change occurred, the aggregate listener did not fire.



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