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

Aravindan Vijayan updated AMBARI-13411:
---------------------------------------
    Description: 
Bug
The metrics data returned by Ambari that is displayed on the charts seems to 
have different granularity for different periods in a single time series on a 
chart.

Problem
The AMS cache layer running on the Ambari server requests the metrics data only 
for the delta period (period for which the data is not present in the cache) to 
the AMS. The bug was that the precision of the data requested (or computed) was 
not taken into account during this delta request.

Objective of this patch
Incorporate the different between precision of the data in the cache and the 
requested data precision while requesting from AMS.

  was:
PROBLEM


Objective of this patch


> Problem in precision handling of metrics returned by AMS
> --------------------------------------------------------
>
>                 Key: AMBARI-13411
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13411
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.1.2
>            Reporter: Siddharth Wagle
>            Assignee: Aravindan Vijayan
>            Priority: Critical
>             Fix For: 2.1.3
>
>
> Bug
> The metrics data returned by Ambari that is displayed on the charts seems to 
> have different granularity for different periods in a single time series on a 
> chart.
> Problem
> The AMS cache layer running on the Ambari server requests the metrics data 
> only for the delta period (period for which the data is not present in the 
> cache) to the AMS. The bug was that the precision of the data requested (or 
> computed) was not taken into account during this delta request.
> Objective of this patch
> Incorporate the different between precision of the data in the cache and the 
> requested data precision while requesting from AMS.



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

Reply via email to