[
https://issues.apache.org/jira/browse/AMBARI-12248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616122#comment-14616122
]
Hudson commented on AMBARI-12248:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3062 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3062/])
AMBARI-12248. Metrics API result set contains a lot of data outside the
requested time range. (swagle) (swagle:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7763a47eb1a7f23aa015de490fd04f976cdce6c8)
*
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/MetricsPaddingMethodTest.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSReportPropertyProviderTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/spi/TemporalInfo.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/AMSReportPropertyProvider.java
*
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java
*
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/PhoenixTransactSQL.java
*
ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/AMSPropertyProviderTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsDownsamplingMethodFactory.java
* ambari-server/src/test/resources/ams/single_host_component_metrics.json
*
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/ganglia/TestStreamProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricReportingAdapter.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/MetricsDownsamplingMethod.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/TemporalInfoImpl.java
*
ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/AbstractMiniHBaseClusterTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AbstractPropertyProvider.java
> Metrics API result set contains a lot of data outside the requested time range
> ------------------------------------------------------------------------------
>
> Key: AMBARI-12248
> URL: https://issues.apache.org/jira/browse/AMBARI-12248
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.0.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Priority: Critical
> Fix For: 2.1.1
>
> Attachments: buggy-cpu-graph-api-call.png
>
>
> When I access the Host Details page for :
> {code}
> http://172.22.76.13:8080/api/v1/clusters/leapsec/hosts/leapsec-rhel6-11.openstacklocal?fields=metrics/cpu/cpu_user[1436028521,1436032121,15],metrics/cpu/cpu_wio[1436028521,1436032121,15],metrics/cpu/cpu_nice[1436028521,1436032121,15],metrics/cpu/cpu_aidle[1436028521,1436032121,15],metrics/cpu/cpu_system[1436028521,1436032121,15],metrics/cpu/cpu_idle[1436028521,1436032121,15]&_=1435698892786
> {code}
> However, look at the screenshot. The start time (1435946268) and using the
> standard +3600 seconds for the end time (1435949868), the following call was
> made:
> {code}
> http://172.22.76.13:8080/api/v1/clusters/leapsec/hosts/leapsec-rhel6-11.openstacklocal?fields=metrics/cpu/cpu_user[1435946268,1435949868,15],metrics/cpu/cpu_wio[1435946268,1435949868,15],metrics/cpu/cpu_nice[1435946268,1435949868,15],metrics/cpu/cpu_aidle[1435946268,1435949868,15],metrics/cpu/cpu_system[1435946268,1435949868,15],metrics/cpu/cpu_idle[1435946268,1435949868,15]&_=1435698626557
> {code}
> This resulted in 13.6MB of data transferred in 12.05s. The result set size
> is exactly consistent with what is in the screenshot.
> Note that this result set contained a bunch of data that are *outside* of the
> time window specified [1435946268,1435949868).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
