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 ECBD610706 for ; Thu, 20 Nov 2014 17:47:33 +0000 (UTC) Received: (qmail 70643 invoked by uid 500); 20 Nov 2014 17:47:33 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 70607 invoked by uid 500); 20 Nov 2014 17:47:33 -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 70595 invoked by uid 99); 20 Nov 2014 17:47:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Nov 2014 17:47:33 +0000 Date: Thu, 20 Nov 2014 17:47:33 +0000 (UTC) From: "Oleg Nechiporenko (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-8399) Alerts UI: Alerts Instances keep storing in DS.Store even after user navigate away 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-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219656#comment-14219656 ] Oleg Nechiporenko commented on AMBARI-8399: ------------------------------------------- 4883 tests complete (7 seconds) 60 tests pending > Alerts UI: Alerts Instances keep storing in DS.Store even after user navigate away > ---------------------------------------------------------------------------------- > > Key: AMBARI-8399 > URL: https://issues.apache.org/jira/browse/AMBARI-8399 > 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-8399.patch > > > There may be huge number of the alert instances. > In big cluster this may cause performance issues. > Example: > cluster with 200 nodes. > every node has 10-20 alert instances. > user navigates to {{host1/alerts}}. 20 alerts are saved to DS.Store. 20 overall > user navigates to {{host2/alerts}}. 15 alerts are saved to DS.Store. 35 overall > ..... > In some moment may be situation when 2000-4000 alerts will be stored on the UI. > *Expected behavior:* > cleanup alert instances models when new list of models is loaded. -- This message was sent by Atlassian JIRA (v6.3.4#6332)