ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18271) Multiple Aggregate Alerts For JournalNode Exist With Some Being Incorrect
Date Tue, 30 Aug 2016 03:38:20 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-18271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Hurley updated AMBARI-18271:
-------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Multiple Aggregate Alerts For JournalNode Exist With Some Being Incorrect
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-18271
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18271
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: trunk
>
>         Attachments: AMBARI-18271.patch
>
>
> When a cluster is being created initially, there are many new alert instances being generated
concurrently. This can lead to a race condition where certain alert types, such as aggregate
alerts, fire several events and end up creating duplicate alert instances.
> Although aggregate alerts are the most common, the flaw is in the alert listener since
it never guarantees uniqueness even though it supports concurrent events.
> This problem is mainly encountered when the cluster is initially created, and therefore
a solution shouldn't impact the rest of the cluster's lifetime. In other words, we shouldn't
cause a degradation the other 99.9% of the time in order to fix this problem.



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

Mime
View raw message