[
https://issues.apache.org/jira/browse/MESOS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934287#comment-14934287
]
Vinod Kone commented on MESOS-3507:
-----------------------------------
{quote}
there is no uniform way of getting a notion of 'awaiting' tasks i.e. expressing
that a framework has more work to do.
{quote}
We do have an API call for frameworks to express this. requestResources().
Instead of having frameworks expose "queued work" endpoints, and having
something on the master (module?) to interpret this data in a uniform way, why
not just have frameworks explicitly and directly provide the intent of needing
more resources via requestResources() call? Resources is a uniform abstraction
that every framework already understands.
> 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)
