VisionSystemsInc / VisionSystemsInc/terra
Number of Workers in CeleryExecutor
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Python
- Stars
- 2
- Forks
- 3
- Avg merge
- 22m
- Merged PRs (30d)
- 1
Description
num_workers is not honored by the CeleryExecutor.
There are numerous technical issues preventing this mechanism from working in the celery case.
Two potential workarounds include:
- Wrapping a task in a chain to make it count as multiple tasks. This will effectively decrease the concurrency rate with respect to a specific task.
- Create multiple routes/keys/queues and run multiple celery worker parents, one for each queue. This has an increased overhead as more worker parents are added.
Contributor guide
No contributing guide indexed for this repository
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 by tracing the CeleryExecutor handling of num_workers and compare it with the executor behavior where worker counts are honored. Reproduce the issue with a Celery task and verify that the configured worker count affects concurrency; the issue provides no file or test path, so locating the relevant implementation and regression coverage is part of the work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100