ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gour Saha (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-17019) Ambari Slider View creates too many objects at a fast rate creating memory pressure on the server and makes the UI super slow
Date Sun, 05 Jun 2016 18:45:59 GMT

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

Gour Saha updated AMBARI-17019:
-------------------------------
    Priority: Critical  (was: Major)

> Ambari Slider View creates too many objects at a fast rate creating memory pressure on
the server and makes the UI super slow
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17019
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17019
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.2.0
>            Reporter: Gour Saha
>            Priority: Critical
>
> Ambari Slider View creates too many objects at a very fast rate creating memory pressure
on the server (eventually can lead to OutOfMemory if the gc cannot keep up) and makes the
UI super slow. It makes the UI practically un-usable. Restarting Ambari Server is the only
way to fix it.
> The following objects are created for every single call to Slider view methods -
> In SliderAppsViewControllerImpl.java -
> h6. Slider Client 
> {code}
>             final SliderClient sliderClient = createSliderClient();
> {code}
> Only one instance of SliderClient should be created and re-used. 
> h6. UserGroupInformation
> {code}
>         sliderUser = UserGroupInformation.getBestUGI(null, loggedInUser);
> {code}
> We need to visit the UGI code to see how we can solve it. One way could be to cache it
for each unique user and reuse them, rather than creating one for each call. Even for a secure
cluster we should be able to re-use until the keytab expires and create one more time when
it does. Or some other better solution than this.



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

Mime
View raw message