You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2015/08/18 23:26:45 UTC
[jira] [Updated] (AMBARI-12654) Create a Caching layer that
provides sliding window behavior for metric requests to Ambari
[ https://issues.apache.org/jira/browse/AMBARI-12654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Wagle updated AMBARI-12654:
-------------------------------------
Attachment: AMBARI-12654-1.patch
> Create a Caching layer that provides sliding window behavior for metric requests to Ambari
> ------------------------------------------------------------------------------------------
>
> Key: AMBARI-12654
> URL: https://issues.apache.org/jira/browse/AMBARI-12654
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Priority: Critical
> Fix For: 2.1.2
>
> Attachments: AMBARI-12654-1.patch
>
>
> _Objectives_:
> - In-memory caching of timeseries data for 1 hour queries.
> - Support of service and dashboard metrics only
> - Cache refresh is for a small segment of data vs requesting 1 hour data every time.
> - On demand cache with sliding window implementation
> - Zero/Null padding data does not appear in the cache
> - Cache functionality can be turned on / off using config knob
> - Caching policy is a cache-as-sor (Cache as System of Record), all queries for Service Metrics will be returned from cache if caching is enabled and query window fits Cache timeseries window, example 1 hour.
> - Host metric queries will still goto AMS, this prevents host specific data to be cached. This decision is based on usage/access pattern from Ambari web UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)