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 0892117E1C for ; Fri, 13 Mar 2015 19:21:39 +0000 (UTC) Received: (qmail 99326 invoked by uid 500); 13 Mar 2015 19:21:38 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 99041 invoked by uid 500); 13 Mar 2015 19:21:38 -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 98914 invoked by uid 99); 13 Mar 2015 19:21:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Mar 2015 19:21:38 +0000 Date: Fri, 13 Mar 2015 19:21:38 +0000 (UTC) From: "Antonenko Alexander (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-10062) Ambari Web Client Makes Request For All Alerts On Specific Alert Page MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-10062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360964#comment-14360964 ] Antonenko Alexander commented on AMBARI-10062: ---------------------------------------------- +1 for the 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)