ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMBARI-12654) Create a Caching layer that provides sliding window behavior for metric requests to Ambari
Date Fri, 25 Sep 2015 21:31:06 GMT

    [ 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 9/25/15 9:30 PM:
-------------------------------------------------------------------

_New configurations supported in ambari.properties_:
|| Property || Default value || Description ||
| server.timeline.metrics.cache.disabled | false | Disable cache |
| server.timeline.metrics.cache.heap.percent | 15 | Max requests cached |
| server.timeline.metrics.cache.entry.ttl.seconds | 3600 | Evict after 1 hour |
| server.timeline.metrics.cache.entry.idle.seconds | 300 | Evict if not retrieved |
| server.timeline.metrics.cache.read.timeout.millis | 10000 | Timeout on a Cache Miss |
| server.timeline.metrics.cache.interval.read.timeout.millis | 5000 | Timeout for update on
Cache hit, requesting last 5 minutes of data on a hit |
| server.timeline.metrics.cache.connect.timeout.millis | 5000 | Connection timeout |
| server.timeline.metrics.cache.catchup.interval | 300000 | Constant fudge factor subtracted
from the cache update requests to account for unavailability of data on the trailing edge
due to buffering.


was (Author: swagle):
_New configurations supported in ambari.properties_:
|| Property || Default value || Description ||
| server.timeline.metrics.cache.disabled | false | Disable cache |
| server.timeline.metrics.cache.heap.percent | 15 | Max requests cached |
| server.timeline.metrics.cache.entry.ttl.seconds | 3600 | Evict after 1 hour |
| server.timeline.metrics.cache.entry.idle.seconds | 300 | Evict if not retrieved |
| server.timeline.metrics.cache.read.timeout.millis | 10000 | Timeout on a Cache Miss |
| server.timeline.metrics.cache.interval.read.timeout.millis | 5000 | Timeout for update on
Cache hist, requesting last 5 minutes of data on a hit |
| server.timeline.metrics.cache.connect.timeout.millis | 5000 | Connection timeout |
| server.timeline.metrics.cache.catchup.interval | 300000 | Constant fudge factor subtracted
from the cache update requests to account for unavailability of data on the trailing edge
due to buffering.

> 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, AMBARI-12654-2.pach
>
>
> _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)

Mime
View raw message