[
https://issues.apache.org/jira/browse/AMBARI-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219885#comment-14219885
]
Hudson commented on AMBARI-8399:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit-docker #290 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/290/])
AMBARI-8399. Alerts UI: Alerts Instances keep storing in DS.Store even after
user navigate away (onechiporenko) (onechiporenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=beccf117a3e002afe39c7f75abdc553b55486d1c)
* ambari-web/test/controllers/main/alerts/alert_instances_controller_test.js
* ambari-web/app/mappers/alert_instances_mapper.js
* ambari-web/test/mappers/alert_instances_mapper_test.js
* ambari-web/app/assets/test/tests.js
* ambari-web/app/controllers/main/alerts/alert_instances_controller.js
> 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)
