Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-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 55CE9109E1 for ; Fri, 9 Aug 2013 18:32:57 +0000 (UTC) Received: (qmail 75449 invoked by uid 500); 9 Aug 2013 18:32:57 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 75430 invoked by uid 500); 9 Aug 2013 18:32:57 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 75422 invoked by uid 99); 9 Aug 2013 18:32:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Aug 2013 18:32:57 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Aug 2013 18:32:52 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=e4A434QLx8+3BAUFLXFXGJMiAE3lZsRF1X0cvVyy8p0=; b=X5Bzk7oEmNFlFlQf4vBhTcBkA6xQLeeZU1CdBKxdXYCk/dZ8EomnQQn2340AVoS26nl8DyWCVbdSexYVnARH0CRPS6BjUOAwlsBybRq18bLcLKTZgkkabGJzdlffMBXf4CmiCjIScECjfhM8GK2NlkXlpyQ0CmGlnEEKOrBqI34=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-3.v29.ch3.sourceforge.com) by sfs-alluradaemon-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1V7rUG-0004UX-7k for allura-dev@incubator.apache.org; Fri, 09 Aug 2013 18:32:32 +0000 Content-Type: multipart/related; boundary="===============4357255135474400776==" MIME-Version: 1.0 To: "[allura:tickets] " <6540@tickets.allura.p.re.sf.net> From: "Dave Brondsema" Reply-To: "[allura:tickets] " <6540@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #6540 Rate-limit import tasks Message-ID:

Date: Fri, 09 Aug 2013 18:32:32 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============4357255135474400776== Content-Type: multipart/alternative; boundary="===============4206002049328608379==" MIME-Version: 1.0 --===============4206002049328608379== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit - **Size**: --> 2 --- ** [tickets:#6540] Rate-limit import tasks** **Status:** open **Labels:** stability import **Created:** Thu Aug 08, 2013 09:14 PM UTC by Dave Brondsema **Last Updated:** Thu Aug 08, 2013 09:14 PM UTC **Owner:** nobody Import tasks can be resource-intensive and potentially abusive. Allow one import per tool type (or importer, perhaps) per project to run at simultaneously. This can be tracked via the `get/set_tool_data`. We'll have to make sure that error handling [#6530] decrements the count when done. Probably best to track an integer rather than a bool, so that its easier to customize if some deployments of Allura want to allow N simultaneous imports. --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============4206002049328608379== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit
  • Size: --> 2

[tickets:#6540] Rate-limit import tasks

Status: open
Labels: stability import
Created: Thu Aug 08, 2013 09:14 PM UTC by Dave Brondsema
Last Updated: Thu Aug 08, 2013 09:14 PM UTC
Owner: nobody

Import tasks can be resource-intensive and potentially abusive. Allow one import per tool type (or importer, perhaps) per project to run at simultaneously. This can be tracked via the get/set_tool_data. We'll have to make sure that error handling [#6530] decrements the count when done. Probably best to track an integer rather than a bool, so that its easier to customize if some deployments of Allura want to allow N simultaneous imports.


Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============4206002049328608379==-- --===============4357255135474400776==--