temporalio / temporalio/temporal
Include in-memory (sync match) backlog in `ApproximateBacklogCount`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
There are some tasks that will never go to the durable backlog, such as queries and Nexus tasks.
In those cases, and in cases where there's a high sync match rate, it's useful to know how many tasks are in the sync match backlog in order to autoscale workers.
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 by tracing the ApproximateBacklogCount entry point and the code that tracks the in-memory sync-match backlog. Read the surrounding tests, if present, to understand the existing count semantics. Done means the reported approximate backlog includes tasks waiting for sync match, including work that does not enter the durable backlog, and supports the autoscaling use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100