apache / apache/dolphinscheduler

[Bug] [dolphinscheduler-worker] Unable to stop tasks in Seatunnel cluster

Open
#15,738 24 comments 0 reactions 0 assignees View on GitHub
bug help wanted
Dominant language
Java
Stars
14.5k
Forks
5.1k
Avg merge
1d 21h
Merged PRs (30d)
29

Description

### Search before asking

- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.

### What happened

我通过DS定时调度,使用Cluster模式启动Seatunnel任务。
然后通过DS页面中“工作流实例”->“操作”->“停止”按钮停止这个Seatunnel任务。

结果是,杀死了SeatunnelClient。
但事实上SeatunnelClient在Cluster模式下,只是讲任务提交到SeatunnelServer,真正执行任务在SeatunnelServer。
所以,杀死SeatunnelClient,只在Local模式下有用。
在Cluster模式下,需要调用Seatunnel提供的rest api -> "/hazelcast/rest/maps/stop-job"。

我本想自己实现在结束Seatunnel任务的同时调用这个接口,但我没有看到dolphinscheduler-task-seatunnel或dolphinscheduler-worker支持这样的扩展。

### What you expected to happen

pass

### How to reproduce

pass

### Anything else

pass

### Version

dev

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

Contributor guide

Open the contributing guide

Research direction

Start by inspecting the dolphinscheduler-task-seatunnel and dolphinscheduler-worker modules, especially the task stop flow. Compare how stopping a Local-mode task differs from Cluster mode, then review the Seatunnel REST endpoint /hazelcast/rest/maps/stop-job. Done means a Cluster-mode stop reaches the SeatunnelServer while Local-mode behavior remains usable.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.