ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aravindan Vijayan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-13863) UI lags and OutOfMemoryError seen in Ambari server after dashboard metrics' time period are changed.
Date Thu, 12 Nov 2015 18:21:11 GMT

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

Aravindan Vijayan updated AMBARI-13863:
---------------------------------------
    Summary: UI lags and OutOfMemoryError seen in Ambari server after dashboard metrics' time
period are changed.  (was: UI lags and OutOfMemoryError seen in Ambari server after dashboard
metrics change.)

> UI lags and OutOfMemoryError seen in Ambari server after dashboard metrics' time period
are changed.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13863
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13863
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.1.2
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>            Priority: Critical
>             Fix For: 2.1.3
>
>
> Problem
> On the Ambari dashboard page, when different time ranges are randomly chosen, the metrics
charts stop responding and an OutOfMemory is seen in the Ambari server logs.
> Bug
> In the AMS cache layer, the logic to update the cache entry map by removing values outside
the given requested time range eventually leads to memory leak.
> Fix
> Change the logic to explicitly by using the iterator.remove() to remove the entries instead
of using the map.clear() method.



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

Mime
View raw message