You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@dolphinscheduler.apache.org by "richardmilles (via GitHub)" <gi...@apache.org> on 2026/08/07 08:25:35 UTC

Re: [I] [Bug] [SeaTunnel] SeaTunnel streaming job status incorrect & task cannot be stopped from DolphinScheduler [dolphinscheduler]

richardmilles commented on issue #17786:
URL: https://github.com/apache/dolphinscheduler/issues/17786#issuecomment-5214513270

   I'd like to take a **narrow** fix for the SeaTunnel Engine (Zeta) path in this issue.
   
   Plan (one PR, scoped to Zeta/`seatunnel.sh`):
   1. Parse SeaTunnel job id from worker logs (`job id: <id>` from SeaTunnel client submit logs)
   2. On cancel: keep process-tree kill, then also run `seatunnel.sh -can <jobId>` so cluster/streaming jobs are actually canceled when killing the client alone is not enough
   
   Flink/Spark engine Yarn cancel and full status polling stay out of this PR.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org