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 1D9CC171C8 for ; Wed, 22 Oct 2014 21:40:52 +0000 (UTC) Received: (qmail 93596 invoked by uid 500); 22 Oct 2014 21:40:52 -0000 Delivered-To: apmail-aurora-dev-archive@aurora.apache.org Received: (qmail 93549 invoked by uid 500); 22 Oct 2014 21:40:52 -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 93538 invoked by uid 99); 22 Oct 2014 21:40:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Oct 2014 21:40:51 +0000 X-ASF-Spam-Status: No, hits=-2001.4 required=5.0 tests=ALL_TRUSTED,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; Wed, 22 Oct 2014 21:40:51 +0000 Received: (qmail 91065 invoked by uid 99); 22 Oct 2014 21:40:30 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Oct 2014 21:40:30 +0000 Received: from mail-wg0-f45.google.com (mail-wg0-f45.google.com [74.125.82.45]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 777031A02FC for ; Wed, 22 Oct 2014 21:40:05 +0000 (UTC) Received: by mail-wg0-f45.google.com with SMTP id m15so4661959wgh.4 for ; Wed, 22 Oct 2014 14:40:28 -0700 (PDT) X-Gm-Message-State: ALoCoQlhGzLa+zN23EuDFipUoJOxk/43evnaGBYsbwzgbGLBlJx+5/X+GUgtwimq9OyPM0V8zSLW MIME-Version: 1.0 X-Received: by 10.194.203.201 with SMTP id ks9mr579420wjc.105.1414014028769; Wed, 22 Oct 2014 14:40:28 -0700 (PDT) Received: by 10.216.155.200 with HTTP; Wed, 22 Oct 2014 14:40:28 -0700 (PDT) Date: Wed, 22 Oct 2014 14:40:28 -0700 Message-ID: Subject: Cron job quota checking From: Maxim Khutornenko To: dev@aurora.incubator.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Hi all, If you run cron jobs AND use resource quota checking for your production jobs please read further. We are planning to remove the existing loophole [1] for cron jobs sliding under the quota check radar. The proposed approach is to count cron job templates towards the production consumption and block at the creation point (i.e. scheduleCronJob, createJob) when a requested change would go over the allocated quota limit. When [1] is implemented your existing production cron jobs will continue to run as before. However, in case your total prod consumption (including service and cron jobs) is near or over the quota limit any attempts to create/update/schedule jobs under the affected role will be blocked. You will have to explicitly free up production resources or bump up the quota value to unblock. Please, speak up if you have any concerns or suggestions. Thanks, Maxim [1] - https://issues.apache.org/jira/browse/AURORA-825