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] [Commented] (AMBARI-8399) Alerts UI: Alerts Instances keep storing in DS.Store even after user navigate away
Date Thu, 20 Nov 2014 17:47:33 GMT

    [ 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)

Mime
View raw message