[
https://issues.apache.org/jira/browse/AURORA-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644454#comment-14644454
]
Joshua Cohen commented on AURORA-156:
-------------------------------------
Given that quota is actually considered "in use" when a task is PENDING, it
seems to me that it makes sense for the UI to reflect that reality. If consumed
quota did not include PENDING tasks, then confusion might ensue when trying to
schedule a task that, based on the state of the UI, it would seem that there is
available quota, but based on the Scheduler's internal state there is actually
not.
We could, potentially break down the quota usage further to call out running
versus pending quota, but I'm not sure if there's tremendous value in that.
Thoughts on this?
> Consumed resources should not include PENDING tasks
> ---------------------------------------------------
>
> Key: AURORA-156
> URL: https://issues.apache.org/jira/browse/AURORA-156
> Project: Aurora
> Issue Type: Story
> Components: Scheduler, UI
> Reporter: brian wickman
> Priority: Trivial
> Labels: newbie
>
> Currently the consumed resources includes PENDING tasks but I argue it should
> only include tasks in active states (i.e. ASSIGNED, STARTING, RUNNING,
> KILLING, RESTARTING, etc.)
> Similarly, quota should only be deducted once we've moved a task into
> ASSIGNED.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
