[
https://issues.apache.org/jira/browse/MESOS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906108#comment-14906108
]
Aaron Carey commented on MESOS-3507:
------------------------------------
The description sums up our use case pretty well: we have multiple different
frameworks scheduling a variety of different jobs of varying sizes (in terms of
RAM and CPU). We wanted to create a scheduler agnostic way of scaling up (and
possibly down) agent nodes. Currently we're relying on metrics like CPU/Mem
utilisation, whilst this is useful, it doesn't tell you how many tasks are
waiting on resources. Knowing this would allow you to spin up more or less
machines to cope with the load and give a better idea of pressure on the system.
As we're using marathon and chronos etc, we couldn't build autoscaling directly
into these schedulers, and only having it built into our in-house framework
would potentially miss many situations (eg if our in house scheduler had no
jobs waiting, it would assume everything is happy, but marathon could have
several jobs still waiting on resources).
> 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)
