temporalio / temporalio/sdk-python
Run different worker types in separate threads
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 241
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 55
Description
Currently, when workflow and activity workers are run in the same process, they share the the same thread (same event loop):
Running these (and Nexus workers when they arrive) in different threads would prevent an async activity that incorrectly does blocking I/O from blocking workflow progress. In addition to limiting blast radius it should make it easier to understand the failure modes.
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 worker setup in temporalio/worker/_worker.py around lines 489-492, where workflow and activity workers currently share an event loop. Trace how worker types are created and coordinated, including the future Nexus workers mentioned in the issue. Done means workflow, activity, and eventually Nexus workers can run in separate threads without blocking one another.
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
- Mostly clear
- Newbie friendliness
- 35/100