Forceful Termination of Running Orchestrations

Open
#111 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
api, backend, distributed-systems

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.

Description

azure-functions Enhancement P1

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

Dominant language
Java
Stars
29
Forks
18
Avg merge
1d 10h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/durabletask-java

All issues in microsoft/durabletask-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.