temporalio / temporalio/temporal-worker-controller
Automatically scale up worker versions with reachability ClosedOnly on query
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 187
- Forks
- 70
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 31
Description
Right now it is hard to scale to zero worker versions that only have closed workflows, while still detecting that queries are being sent to those versions and scaling back up when necessary.
The TaskAddRate statistic from the DescribeTaskQueue API does include query tasks, but is not guaranteed to catch sporadic queries (eg. due to a human debugging a single closed workflow execution).
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 reviewing the Temporal DescribeTaskQueue API and its TaskAddRate statistic, focusing on how query tasks and sporadic queries are represented. Define how ClosedOnly worker versions should scale up when queries arrive, including behavior for queries that TaskAddRate does not capture; done means closed-only versions can reliably scale back up when queried.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100