apache / apache/dolphinscheduler

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

Open
#17,786 14 comments 0 reactions 0 assignees View on GitHub
backend bug help wanted priority:middle
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

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:
Image

seatunnel webui:
Image

### Anything else

_No response_

### Version

3.2.x

### Are you willing to submit PR?

- [x] 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

No files, tests, or code entry points are named. Start by reproducing a SeaTunnel MySQL-CDC streaming job through DolphinScheduler, then trace how its runtime status and Stop action are handled; done means DolphinScheduler and SeaTunnel report consistent status and stopping the task terminates the SeaTunnel job.

Written by the indexing model from the issue text.

Assessment

Tech stack
mysql
Domain
data-engineering, stream-processing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
46/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.