[
https://issues.apache.org/jira/browse/AMBARI-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643152#comment-14643152
]
Hudson commented on AMBARI-12554:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3178 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3178/])
AMBARI-12554. FE: Switching between different service's configs does not reduce
DOM node and listeners count (akovalenko) (akovalenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=892ef84772c3b096ec24da94050a79966e0d6c33)
* ambari-web/app/views/common/configs/service_config_view.js
* ambari-web/app/utils/helper.js
* ambari-web/app/controllers/main/service/info/configs.js
> 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
>
> Attachments: AMBARI-12554.patch
>
>
> 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)
