ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksandr Kovalenko (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (AMBARI-12554) FE: Switching between different service's configs does not reduce DOM node and listeners count
Date Mon, 27 Jul 2015 16:19:05 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aleksandr Kovalenko reassigned AMBARI-12554:
--------------------------------------------

    Assignee: Aleksandr Kovalenko

> FE: Switching between different service's configs does not reduce DOM node and listeners
count
> ----------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-12554
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12554
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.1
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>            Priority: Critical
>             Fix For: 2.1.1
>
>
> Was profiling Ambari-2.1.0 latest build and switching between service's and their configuration
tabs. The path I took was HDFS (Settings) > HDFS (Advanced) > YARN (Settings) > YARN
(Advanced) > Hive (Settings) > Hive (Advanced), and back to HDFS. 
> This route resulted in 122K DOM nodes becoming 219K DOM nodes. Also 159 listeners became
606 listeners. This was after garbage collection was done. It looks like once we go a service's
configs page and leave it, we are leaving behind DOM nodes and listeners, which keep accumulating
and bloating the app.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message