You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Cory Johns <ma...@users.sf.net> on 2013/09/09 16:36:22 UTC
[allura:tickets] #6540 Rate-limit import tasks
- **status**: open --> in-progress
- **assigned_to**: Cory Johns
---
** [tickets:#6540] Rate-limit import tasks**
**Status:** in-progress
**Labels:** stability import
**Created:** Thu Aug 08, 2013 09:14 PM UTC by Dave Brondsema
**Last Updated:** Fri Aug 23, 2013 07:12 PM UTC
**Owner:** Cory Johns
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.