apache/dolphinscheduler

[Bug] [SeaTunnel] SeaTunnel streaming job status incorrect & task cannot be stopped from DolphinScheduler

Open

#17786 opened on Dec 12, 2025

View on GitHub
 (12 comments) (0 reactions) (0 assignees)Java (11,659 stars) (4,324 forks)batch import
backendbughelp wantedpriority:middle

Description

Search before asking

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

What happened

version: 3.2.2

When running a SeaTunnel MySQL-CDC streaming job through DolphinScheduler, the task status shown in DolphinScheduler UI is incorrect, and the “Stop” action does not actually terminate the running SeaTunnel job.

This causes DolphinScheduler to report the workflow as “Stopped”, while the SeaTunnel job continues running in the background.

What you expected to happen

Expected behavior

DolphinScheduler should display the correct runtime status of a streaming task.

When clicking Stop, DolphinScheduler should send the appropriate stop/kill command to SeaTunnel so the job is actually terminated.

Task status in DolphinScheduler and SeaTunnel should remain consistent.

Actual behavior

DolphinScheduler shows the task as Executing or Started workflow, even though the SeaTunnel job is already running normally.

Clicking Stop in DolphinScheduler does not terminate the SeaTunnel job.

SeaTunnel UI still shows the job in RUNNING state.

DolphinScheduler UI incorrectly reports the task as Stopped, leading to mismatch between DS and SeaTunnel.

How to reproduce

Screenshots

dolphin webui：

seatunnel webui:

Anything else

No response

Version

3.2.x

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Contributor guide

Tech stack
java
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of Apache DolphinScheduler task lifecycleFamiliarity with SeaTunnel streaming jobsJava development skills
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the DolphinScheduler task status update logic for streaming tasks, specifically in the SeaTunnel task plugin. Examine the stop/kill command flow from DolphinScheduler to SeaTunnel. Check if the SeaTunnel job ID is correctly tracked and if the stop API is called. Look at the status polling mechanism for task synchronization. The issue may require changes in both the DolphinScheduler executor and the SeaTunnel connector.