Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F225317724 for ; Tue, 24 Feb 2015 21:23:04 +0000 (UTC) Received: (qmail 11271 invoked by uid 500); 24 Feb 2015 21:23:04 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 11230 invoked by uid 500); 24 Feb 2015 21:23:04 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 11218 invoked by uid 99); 24 Feb 2015 21:23:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Feb 2015 21:23:04 +0000 Date: Tue, 24 Feb 2015 21:23:04 +0000 (UTC) From: "Jonathan Hurley (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-9781) Aggregate Alerts Are Not Calculated When Receiving the Initial Alert Instance MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jonathan Hurley created AMBARI-9781: --------------------------------------- Summary: 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 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)