microsoft / microsoft/durabletask-java
Forceful Termination of Running Orchestrations
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 29
- Forks
- 18
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
Today, terminate API is an async API. So if there's an instance running and we call /terminate, the framework return with "Accepted". However, in the background if the activity function is taking time, the terminate may take time depending on the activities (Please confirm my understanding here).
I need a way to terminate the orchestration instance forcefully that would stop all the running activity functions forcefully, or have a function "stop" in activity definitions that guide the behaviour of activities in case a forceful terminate is called.
Essentially, an API might look like this /terminate?force=true
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 no files, tests, or entry points. Start by tracing the terminate API and the background activity behavior described; done requires a decided force-termination contract, including how running activities should behave.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100