[
https://issues.apache.org/jira/browse/MESOS-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710330#comment-13710330
]
Benjamin Mahler commented on MESOS-375:
---------------------------------------
Circling back, I like benh's suggestion to drive the collection externally.
However, this potentially conflicts with the goal of this ticket, since we
would only be storing resource usage information when an external request is
made.
Here's what I've been thinking for this ticket:
* Keep collecting periodically, this could be minutely (for historical
purposes) + driven by external requests (for the current information).
* Add a /monitor/series.json endpoint to make it easier to obtain historical
usage information.
* Improve the statistics API to guard against excessive memory consumption.
> Keep the stats for tasks around after the tasks are archived
> ------------------------------------------------------------
>
> Key: MESOS-375
> URL: https://issues.apache.org/jira/browse/MESOS-375
> Project: Mesos
> Issue Type: Bug
> Reporter: Florian Leibert (flo)
> Assignee: Benjamin Mahler
>
> We would like to ship chronos with task stats, however many of our tasks
> finish within a second or so and thus requests to <slave>/monitor/usage.json
> often no longer show the task.
> Could we get these stats for a variable window even after the task got
> scheduled?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
