incubator-mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Hindman (JIRA)" <>
Subject [jira] [Commented] (MESOS-375) Keep the stats for tasks around after the tasks are archived
Date Mon, 04 Mar 2013 01:12:11 GMT


Benjamin Hindman commented on MESOS-375:

Hmm. I think it would make sense to drive the actual collection when a request is made. The
consumers of this interface would then be both the slave itself (i.e., collecting on behalf
of the master) and any external services such as a TSDB (or, until we add it into the API,
a scheduler). Given the power of futures it should be trivial to "batch" requests that arrive
near one another together so as not to overload the isolation modules doing the actual collecting
(that is to say, only queue up collection requests as fast as the statistics can actually
be gathered).

Related, exposing statistics that are based on the collection interval (e.g., cpu_time) WITHOUT
exposing the collection interval makes those statistics useless. ;)
> Keep the stats for tasks around after the tasks are archived
> ------------------------------------------------------------
>                 Key: MESOS-375
>                 URL:
>             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:

View raw message