You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Michael Browning (JIRA)" <ji...@apache.org> on 2016/04/25 20:40:13 UTC

[jira] [Issue Comment Deleted] (MESOS-4760) Expose metrics and gauges for fetcher cache usage and hit rate

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

Michael Browning updated MESOS-4760:
------------------------------------
    Comment: was deleted

(was: Great, I'll get on that. One question to guide my implementation: I discovered the need for this so that metrics could be correctly implemented, but other than that, what was the motivation for refactoring fetcher/agent/containerizer this way?)

> Expose metrics and gauges for fetcher cache usage and hit rate
> --------------------------------------------------------------
>
>                 Key: MESOS-4760
>                 URL: https://issues.apache.org/jira/browse/MESOS-4760
>             Project: Mesos
>          Issue Type: Improvement
>          Components: fetcher, statistics
>            Reporter: Michael Browning
>            Assignee: Michael Browning
>            Priority: Minor
>              Labels: features, fetcher, statistics, uber
>
> To evaluate the fetcher cache and calibrate the value of the fetcher_cache_size flag, it would be useful to have metrics and gauges on agents that expose operational statistics like cache hit rate, occupied cache size, and time spent downloading resources that were not present.



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