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 899DA1742B for ; Fri, 13 Mar 2015 20:48:38 +0000 (UTC) Received: (qmail 46462 invoked by uid 500); 13 Mar 2015 20:48:38 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 46421 invoked by uid 500); 13 Mar 2015 20:48: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 46399 invoked by uid 99); 13 Mar 2015 20:48: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 20:48:38 +0000 Date: Fri, 13 Mar 2015 20:48:38 +0000 (UTC) From: "Hudson (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=14361064#comment-14361064 ] Hudson commented on AMBARI-10062: --------------------------------- ABORTED: Integrated in Ambari-branch-2.0.0 #70 (See [https://builds.apache.org/job/Ambari-branch-2.0.0/70/]) AMBARI-10062. Ambari Web Client Makes Request For All Alerts On Specific Alert Page (onechiporenko) (onechiporenko: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4c8b6b10dce8181a9a797b4a7f09d4e09bbb826a) * ambari-web/app/models/service.js * ambari-web/app/templates/application.hbs * ambari-web/test/controllers/main/alert_definitions_controller_test.js * ambari-web/app/utils/ember_reopen.js * ambari-web/app/utils/ajax/ajax.js * ambari-web/app/mixins/common/table_server_mixin.js * ambari-web/app/styles/common.less * ambari-web/test/controllers/main/alerts/alert_instances_controller_test.js * ambari-web/app/controllers/global/update_controller.js * ambari-web/app/views/main/alerts/definition_details_view.js * ambari-web/app/templates/main/alerts/definition_details.hbs * ambari-web/app/views/main/host.js * ambari-web/app/controllers/main/alerts/alert_instances_controller.js * ambari-web/app/controllers/main/alert_definitions_controller.js * ambari-web/app/templates/common/modal_popups/alerts_popup.hbs * ambari-web/app/styles/application.less * ambari-web/app/templates/main/host.hbs > 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, AMBARI-10062_branch-2.0.0.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)