Add an configuration option to cap task group workers usage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Is your feature request related to a problem? Please describe.
Depening on the action, task group can spawn X tasks that will consume all workers and stall whole pulp installation.
Example: ACS task group will create as many tasks as there are repos to refresh.
As a result all workers could be occupied and pulp will not be usable
Describe the solution you'd like
Potentially as an config option that will globally limit how many workers each task group could consume at a time so leave spare resources for other pulp actions - sync, upload, copy, publish, etc.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Here's a brainstorming doc https://hackmd.io/@ggainey/task_throttling_thoughts
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked task-throttling brainstorming document and the task-group worker behavior described in the issue. Define the configuration's scope and semantics, then verify that a task group is capped while spare workers remain available for other Pulp actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100