[
https://issues.apache.org/jira/browse/AMBARI-12654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700400#comment-14700400
]
Siddharth Wagle edited comment on AMBARI-12654 at 8/17/15 11:19 PM:
--------------------------------------------------------------------
_New configurations supported in ambari.properties_:
|| Property || Default value ||
| server.timeline.metrics.cache.disabled | false |
| server.timeline.metrics.cache.max.entries | 1000 |
| server.timeline.metrics.cache.entry.ttl.seconds | 3600 |
| server.timeline.metrics.cache.entry.idle.seconds | 300 |
| server.timeline.metrics.cache.read.timeout.millis | 10000 |
| server.timeline.metrics.cache.read.timeout.millis | 5000 |
| server.timeline.metrics.cache.connect.timeout.millis | 5000 |
| server.timeline.metrics.cache.catchup.interval | 300000 |
was (Author: swagle):
_New configurations added to ambari.properties_:
|| Property || Default value ||
| server.timeline.metrics.cache.disabled | false |
| server.timeline.metrics.cache.max.entries | 1000 |
| server.timeline.metrics.cache.entry.ttl.seconds | 3600 |
| server.timeline.metrics.cache.entry.idle.seconds | 300 |
| server.timeline.metrics.cache.read.timeout.millis | 10000 |
| server.timeline.metrics.cache.read.timeout.millis | 5000 |
| server.timeline.metrics.cache.connect.timeout.millis | 5000 |
| server.timeline.metrics.cache.catchup.interval | 300000 |
> 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
>
>
> _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)
