temporalio / temporalio/temporal
Support workflow task completions larger than gRPC max message size
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Describe the solution you'd like
Today when a > 4MB gRPC request is sent, server fails. SDK side is making the failures non-retryable in https://github.com/temporalio/features/issues/624, but a solution is needed to actually make large tasks work. It is to be determined whether this is splitting a single task response into multiple calls or multiple tasks or some other approach.
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 reviewing the gRPC request-size failure described in this issue and the related SDK behavior in features/624. The issue leaves the implementation approach open, so compare splitting one task response, using multiple tasks, and other approaches before defining the scope. Done means workflow task completions larger than 4 MB work without the server failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100