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-14007) Fix precision issues in AMS.
Date Sun, 22 Nov 2015 22:48:11 GMT

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

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

> Fix precision issues in AMS.
> ----------------------------
>
>                 Key: AMBARI-14007
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14007
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.1.2
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-14007.patch
>
>
> Problem
> The following error is seen in the ambari server log when different time periods are
selected in the Host page.
> 19 Nov 2015 22:27:50,476 ERROR [qtp-client-79] MetricsRequestHelper:96 - Error getting
timeline metrics : {"exception":"BadRequestException","message":"java.lang.Exception: Requested
precision (SECONDS) for given time range causes result set size of 15840, which exceeds the
limit - 11520. Please request higher precision.","javaClassName":"org.apache.hadoop.yarn.webapp.BadRequestException"}
> Bug
> The default metric service result limit of 11520 was not able to satisfy a couple of
specific cases of 22 host metrics requested for 2 hours in SECONDS precision.
> Fix
> Change default limit to15840. Covers all time periods of all metric charts in Ambari
web. Introduce a simple 1 time retry mechanism in Ambari server according to which the server
retries AMS with the same request with higher precision if a request fails due to PrecisionLimitExceededException.



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

Mime
View raw message