DhiyaneshwaranR commented on issue #17106: URL: https://github.com/apache/dolphinscheduler/issues/17106#issuecomment-2816885850
Hi @ws752499660 Thanks for raising this! Just to clarify — starting from DolphinScheduler v3.3.0-alpha, the task kill logic has already been improved as part of [PR #17005](https://github.com/apache/dolphinscheduler/pull/17005). It now follows a graceful shutdown sequence: `SIGINT → SIGTERM → SIGKILL` So: • If a task supports graceful termination (e.g., Java with shutdown hooks), it will now handle that properly via SIGINT. • SIGKILL is only used as a last resort if the earlier signals fail. At the moment, configuring or customizing the kill signal (globally or per-task) is not available — it follows the fixed order above. @SbloodyS would it still make sense to work on this as a configurable feature, or should we consider this already resolved since the graceful signal flow is now in place? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
