#6540 Rate-limit import tasks

asf_release_1.0.1
closed
Cory Johns
General
2015-04-04
2013-08-08
Dave Brondsema
No

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.

Related

Tickets: #6530
Tickets: #6624

Discussion

  • Dave Brondsema
    Dave Brondsema
    2013-08-09

    • Size: --> 2
     
  • Dave Brondsema
    Dave Brondsema
    2013-08-23

    • Milestone: forge-aug-23 --> forge-sep-06
     
  • Dave Brondsema
    Dave Brondsema
    2013-08-23

    • Milestone: forge-sep-06 --> forge-sep-20
     
  • Cory Johns
    Cory Johns
    2013-09-09

    • status: open --> in-progress
    • assigned_to: Cory Johns
     
    • assigned_to: Cory Johns --> Tim Van Steenburgh
     
  • Cory Johns
    Cory Johns
    2013-09-09

    • assigned_to: Tim Van Steenburgh --> Cory Johns
     
  • Cory Johns
    Cory Johns
    2013-09-10

    • status: in-progress --> code-review
     
  • Cory Johns
    Cory Johns
    2013-09-10

    allura:cj/6540
    forge-classic:cj/6540
    googlecodewikiimporter:cj/6540
    tracwikiimporter:cj/6540

     
  • Dave Brondsema
    Dave Brondsema
    2013-09-12

    • QA: Dave Brondsema
     
  • Dave Brondsema
    Dave Brondsema
    2013-09-13

    • status: code-review --> closed