You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2016/08/29 16:35:20 UTC

[jira] [Updated] (AMBARI-18271) Multiple Aggregate Alerts For JournalNode Exist With Some Being Incorrect

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

Jonathan Hurley updated AMBARI-18271:
-------------------------------------
    Fix Version/s:     (was: 2.5.0)
                   trunk

> 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
>
>
> 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)