ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Nechiporenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-10062) Ambari Web Client Makes Request For All Alerts On Specific Alert Page
Date Fri, 13 Mar 2015 17:52:38 GMT

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

Oleg Nechiporenko updated AMBARI-10062:
---------------------------------------
    Attachment: AMBARI-10062.patch

> Ambari Web Client Makes Request For All Alerts On Specific Alert Page
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-10062
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10062
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-10062.patch
>
>
> When you click on an alert in order to see all instances of that alert, the web client
makes the following request:
> {{/api/v1/clusters/perf400/alerts?fields=*&(Alert/definition_id=9|Alert/state.in(CRITICAL,WARNING))&_=1426189130461}}
> Here it's asking for all alert instances for definition 9 OR all alerts in the system
that are CRITICAL/WARNING.
> I clicked on the alert for definition 9, and I only expect to see alerts for that definition.
The 2nd part of the query (the OR) gets all alert instances. In a large cluster, this is a
performance problem.



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

Mime
View raw message