You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Diego Santesteban (JIRA)" <ji...@apache.org> on 2017/12/04 14:01:01 UTC
[jira] [Created] (AMBARI-22581) Aggregate alert includes a deleted
component in its "total" count
Diego Santesteban created AMBARI-22581:
------------------------------------------
Summary: Aggregate alert includes a deleted component in its "total" count
Key: AMBARI-22581
URL: https://issues.apache.org/jira/browse/AMBARI-22581
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.0
Environment: OS: Red Hat 7.2
Arch: Power
Reporter: Diego Santesteban
Priority: Minor
Fix For: trunk
In IBM Big SQL, we have included several alerts. One is an aggregate alert which reports how many of our "slave" components are running.
In the cluster (originally installed with one master and three slave components), the slave component was removed from one host, and the individual alert on that host was removed, but the aggregate alert still shows three slave components in total, and fires the alert because it can only find two of them as "OK".
Then, when we trigger an alert event (by stopping one of the remaining slave components) the alert is updated to show the new, correct total count.
Judging by all of this, it sounds like we just need to make deleting a component an "alert event" for any alerts that were associated with that component. The event will trigger an update of the aggregate alert.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)