[
https://issues.apache.org/jira/browse/MESOS-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592510#comment-13592510
]
Benjamin Mahler commented on MESOS-375:
---------------------------------------
I'm not sold on that approach, given the slave might be disconnected from the
master. In that case, it should still be collecting in the background IMO.
On your second note, cpu_time is total, just a sum of the user_time and
system_time, so these are not related to the collection interval. cpu_usage,
however, is related but remains usable without the collection interval. Still,
I should expose the collection interval for cpu_usage to be fully appreciated ;)
> 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
> Priority: Blocker
>
> 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
