temporalio / temporalio/sdk-java
Log activity thread stack trace if it times out or fails to heartbeat
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem? Please describe.
It is common for activities to fail to heartbeat on time or complete an activity on time. Troubleshooting this problem is not simple.
Describe the solution you'd like
Automatically log the stack of the activity thread if an activity didn't heartbeat within heartbeat interval or an activity failed to complete for the start to close timeout.
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 locating the activity execution paths that handle missed heartbeats and start-to-close timeouts. Trace how those failures are currently reported, then define completion as logging the activity thread stack for both cases and verify the behavior with the relevant activity timeout and heartbeat tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100