temporalio / temporalio/sdk-java
Query is not picked up by the worker executing local activity for more than a minute
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
Currently client query calls that "hang" (don't return a result) do that for 60 seconds (max workflow task timeout?) at which point client gets delivered WorkflowServiceException that includes StatusRuntimeException (context deadline exceeded).
The client call should instead fail with WorkflowServiceException according to rpcTimeout (default 10s).
Not a proper sdk sample, but https://gist.github.com/tsurdilo/57282199bc8534c3838252f1c4bf58fc
shows this (query hangs for 60 seconds while local activity is retrying).
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 with the linked reproduction gist and trace how a client query behaves while a local activity is retrying. Verify the timeout used for the query against the default rpcTimeout and confirm that the client receives WorkflowServiceException after about 10 seconds rather than waiting 60 seconds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100