apache/dolphinscheduler

[Feature][Task - kill task] Support user to config kill signal type of killing process/task

Open

#17106 opened on Apr 3, 2025

View on GitHub
 (3 comments) (0 reactions) (1 assignee)Java (11,659 stars) (4,324 forks)batch import
UIbackendfeaturehelp wanted

Description

Search before asking

  • I had searched in the issues and found no similar feature requirement.

Description

I noticed that if user try to kill the task/process, for example, a Java task, dophin scheduler will send "kill -9" which is "SIGKILL" signal to java worker process.

Would you please make the kill signal be configable? Becasue in some situation, we want worker process to send "I am killed" message to specific observer application or do something else to clean resource when user try to kill task/process via dophin scheduler. And if the worker process is killed by ""SIGKILL" signal, there is no chance for "JVM runtime hook" to do something when the process needed to exit.

Thererfore, would you please make the kill signal be configable? Thanks for your help.

Use case

User can be config the kill signal type of specific work process/task.

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Contributor guide

Tech stack
java
Domain
backenddevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaLinux process signalsDolphinScheduler configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate how DolphinScheduler kills tasks (e.g., in `ProcessTask` or `YarnTaskExecutor`). Identify where the signal is hardcoded (likely `kill 9`). Propose adding a configuration property like `task.kill.signal` in `application.yaml`. Consider allowed values (e.g., SIGTERM, SIGKILL). Ensure backward compatibility (default SIGKILL). Update relevant classes to read the property and use the specified signal. Test with different task types.