[
https://issues.apache.org/jira/browse/MESOS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906266#comment-14906266
]
Aaron Carey commented on MESOS-3507:
------------------------------------
As an interesting side note: it'd also be useful for us to see what kind of
resources tasks are waiting for, for example we have some machines with GPUs
in, which utilise a resource on the mesos-agent, thus no amount of launching
non-gpu instances would help these tasks!
> As an operator, I want a way to inspect queued tasks in running schedulers
> --------------------------------------------------------------------------
>
> Key: MESOS-3507
> URL: https://issues.apache.org/jira/browse/MESOS-3507
> Project: Mesos
> Issue Type: Story
> Reporter: Niklas Quarfot Nielsen
>
> Currently, there is no uniform way of getting a notion of 'awaiting' tasks
> i.e. expressing that a framework has more work to do. This information is
> useful for auto-scaling and anomaly detection systems. Schedulers tend to
> expose this over their own http endpoints, but the format across schedulers
> are most likely not compatible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
