Return-Path: X-Original-To: apmail-aurora-dev-archive@minotaur.apache.org Delivered-To: apmail-aurora-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1D6FB105DB for ; Thu, 26 Feb 2015 19:26:57 +0000 (UTC) Received: (qmail 65964 invoked by uid 500); 26 Feb 2015 19:26:35 -0000 Delivered-To: apmail-aurora-dev-archive@aurora.apache.org Received: (qmail 65915 invoked by uid 500); 26 Feb 2015 19:26:35 -0000 Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.incubator.apache.org Delivered-To: mailing list dev@aurora.incubator.apache.org Received: (qmail 65904 invoked by uid 99); 26 Feb 2015 19:26:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Feb 2015 19:26:34 +0000 X-ASF-Spam-Status: No, hits=-1997.8 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 26 Feb 2015 19:26:33 +0000 Received: (qmail 65837 invoked by uid 99); 26 Feb 2015 19:26:13 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Feb 2015 19:26:13 +0000 Received: from mail-qg0-f47.google.com (mail-qg0-f47.google.com [209.85.192.47]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 319991A0458 for ; Thu, 26 Feb 2015 19:26:12 +0000 (UTC) Received: by mail-qg0-f47.google.com with SMTP id f51so2712284qge.6 for ; Thu, 26 Feb 2015 11:26:11 -0800 (PST) X-Gm-Message-State: ALoCoQkkVHO0lkedwlbrONAybkO6+TxhbkFjIFAHBoJwfAfFLTJ3E2wUwVZ2NiCORQjEuzdHxsOZ MIME-Version: 1.0 X-Received: by 10.140.34.36 with SMTP id k33mr20781380qgk.66.1424978771423; Thu, 26 Feb 2015 11:26:11 -0800 (PST) Received: by 10.229.139.195 with HTTP; Thu, 26 Feb 2015 11:26:11 -0800 (PST) In-Reply-To: References: Date: Thu, 26 Feb 2015 11:26:11 -0800 Message-ID: Subject: Re: Insufficient resource quota when production is True From: Bill Farner To: "dev@aurora.incubator.apache.org" Content-Type: multipart/alternative; boundary=001a11c0caf27bfdf9051002b98f X-Virus-Checked: Checked by ClamAV on apache.org --001a11c0caf27bfdf9051002b98f Content-Type: text/plain; charset=UTF-8 This is, unfortunately, only sparsely documented [1]: Whether or not this is a production task backed by quota (Default: False). > Production jobs may preempt any non-production job, and may only be > preempted by production jobs in the same role and of higher priority. To > run jobs at this level, the job role must have the appropriate quota. What we neglect to mention is how one is granted quota. This is done with the aurora_admin command. The idea here is that cluster administrators make decisions about the amount of resources to guarantee to specific users. $ aurora_admin set_quota F0226 11:24:42.838977 19912 base.py:39] usage: set_quota cluster role cpu ram[MGT] disk[MGT] [1] https://github.com/apache/incubator-aurora/blob/master/docs/configuration-reference.md#job-objects -=Bill On Thu, Feb 26, 2015 at 11:17 AM, Larry Weya wrote: > I have a pretty basic job > > prod_resources = Resources(cpu = 0.5, ram = 256*MB, disk=2000*MB) > My cluster has 3 slaves, each with 4 cpu cores and 16GB or RAM but I'me > getting > > Job creation failed due to error: > > Insufficient resource quota: CPU quota exceeded by 1.00 core(s); RAM quota > exceeded by 512.00 MB; DISK quota exceeded by 4000.00 MB > This only happens when I set production to true in the job configuration, > otherwise, the jobs run fine. > > -- > Larry Weya > --001a11c0caf27bfdf9051002b98f--