Hi, @James As far as I know, when the framework request offer, master/messages_resource_request would increment. And when the framework accept the offer and launch tasks, master/messages_launch_tasks would increment. But mesos don't know how many tasks pending in framework, because I think this information is maintained by framework. But I think you still could through (master/messages_resource_request - master/messages_launch_tasks) to deduce the pending status. While (master/messages_resource_request - master/messages_launch_tasks) is not equal to actual pending tasks number.
On Wed, Sep 23, 2015 at 4:51 PM, James Vanns <[email protected]> wrote: > Hi all. It appears there is a glaring omission in the 'Tasks' section of > the following doc; > > http://mesos.apache.org/documentation/latest/monitoring/ > > Shouldn't there be a 'Tasks waiting' metric!? We generally have tasks > hanging around for > a while because their resource requests can't (yet) be met by any offer - > so we'd like a > counter for how many!? Did I miss something? > > Also, what about near-real-time metrics of a running task? Eg. resource > consumption (n% of > CPUs asked for, 8GB/12GB allocated etc.). Can we get that information? > > Cheers, > > Jim > > -- > Senior Code Pig > Industrial Light & Magic > -- Best Regards, Haosdent Huang
