ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (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 18:19:33 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219702#comment-14219702
] 

Hadoop QA commented on AMBARI-8399:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12682694/AMBARI-8399.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/707//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/707//console

This message is automatically generated.

> 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