temporalio / temporalio/temporal-worker-controller
Optimization: Requeue sooner when new deployment version has just started polling but isn’t “active” yet
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 187
- Forks
- 70
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 31
Description
Right now we reconcile every 30s, and have to wait at least this long after new worker pods begin polling before we can observe the new version through the Temporal API.
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 with the reconciliation loop that currently waits for the 30-second interval and the Temporal API polling path. Trace how a newly started deployment version is observed before it becomes active. Done means the controller requeues sooner after polling begins, with coverage for the earlier observation timing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100