You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Joe Smith (JIRA)" <ji...@apache.org> on 2015/06/26 20:21:04 UTC
[jira] [Created] (AURORA-1375) When setting quota, the scheduler
should prevent setting below current usage
Joe Smith created AURORA-1375:
---------------------------------
Summary: When setting quota, the scheduler should prevent setting below current usage
Key: AURORA-1375
URL: https://issues.apache.org/jira/browse/AURORA-1375
Project: Aurora
Issue Type: Story
Components: Scheduler
Reporter: Joe Smith
Initially I thought this check should live in the admin client, but after discussing with [~zmanji], we believe the scheduler would be the right place to enforce this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [jira] [Created] (AURORA-1375) When setting quota, the scheduler
should prevent setting below current usage
Posted by Kevin Sweeney <ks...@twitter.com.INVALID>.
This should be much easier now that we're using a relational database - we
can add a CHECK constraint.
On Fri, Jun 26, 2015 at 11:21 AM, Joe Smith (JIRA) <ji...@apache.org> wrote:
> Joe Smith created AURORA-1375:
> ---------------------------------
>
> Summary: When setting quota, the scheduler should prevent
> setting below current usage
> Key: AURORA-1375
> URL: https://issues.apache.org/jira/browse/AURORA-1375
> Project: Aurora
> Issue Type: Story
> Components: Scheduler
> Reporter: Joe Smith
>
>
> Initially I thought this check should live in the admin client, but after
> discussing with [~zmanji], we believe the scheduler would be the right
> place to enforce this.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>
--
Kevin Sweeney
@kts