temporalio / temporalio/temporal
History service should pause accepting new signals if worker cannot keep up.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
History service should pause accepting new signals if worker cannot keep up.
Describe the solution you'd like
Pause functionality, in case worker cannot keep up with the incoming events.
Describe alternatives you've considered
N/A
Additional context
N/A
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
The issue names the history service, incoming signals, and its worker, but no files, tests, or entry points. Start by locating the history service's signal intake and worker handling, then clarify how pausing should work and what worker state should resume acceptance; done requires an agreed behavior and tests for a worker that cannot keep up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100