[
https://issues.apache.org/jira/browse/MESOS-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259267#comment-15259267
]
Michael Browning commented on MESOS-4760:
-----------------------------------------
Diff (note, this is a sketch, not intended for merging) of what the changes
would look like:
https://reviews.apache.org/r/46717/
Most of these depend pretty heavily on unification with {{uri::Fetcher}}, since
a lot of the relevant information is only accessible to the {{mesos-fetcher}}
binary, which is the only entity that knows whether the URI is being fetched
from the cache or not. To that end, I think they'll have to wait for further
progress on the work that [~kaysoky] is doing, after which I can proceed with
making the Fetcher an injected property in the Slave process, which will allow
it to expose methods for the new metrics added in {{slave/metrics.cpp}}.
> 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)
