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 periods are changed.
Date Fri, 13 Nov 2015 00:42:11 GMT

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

Aravindan Vijayan updated AMBARI-13863:
---------------------------------------
    Attachment: AMBARI-13863.patch

> UI lags and OutOfMemoryError seen in Ambari server after dashboard metrics' time periods
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
>
>         Attachments: AMBARI-13863.patch
>
>
> 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 pad the cache entry map by looking at the delta
between the values present in the map. When there is only one data point, it assumes a default
pad interval of 15 seconds even if the actual data precision could be in minutes/hours/days.
> Fix
> Change the padding interval logic to use the precision calculated using the requested
start and end time. If the precision is in SECONDS, the delta between the values in the map
are used.



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

Mime
View raw message