Mrhs121 commented on issue #17786: URL: https://github.com/apache/dolphinscheduler/issues/17786#issuecomment-3653998222
> I tried to switch the cancellationApplication() method implementation in SeatunnelTask in 3.3.1 and 3.2.2. In the old version 3.3.1, process.destroy() and process.destroyForcibly() were used, but in 3.3.2, it was changed to ProcessUtils.kill(). Is it because of this fix? [@ruanwenjun](https://github.com/ruanwenjun) > > Comparison screenshots: <img alt="Image" width="1323" height="390" src="https://private-user-images.githubusercontent.com/45968542/526380829-ff23a5e1-b73d-4ee7-97a8-a0c8a329413e.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjU3ODMyMzAsIm5iZiI6MTc2NTc4MjkzMCwicGF0aCI6Ii80NTk2ODU0Mi81MjYzODA4MjktZmYyM2E1ZTEtYjczZC00ZWU3LTk3YTgtYTBjOGEzMjk0MTNlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTEyMTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUxMjE1VDA3MTUzMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE1NWZmYmY2OTJlNmJlZTBlMDE4ZDY4MjkyNjljZTY4ZmY1YTY5NzEyMzgxM2UyNmI0NGJlZmY0NjE3N2EyMWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.4k-oW-iGy5ClqIYRuzoMKV8JEe9hG26Vc-G3Flwk7YM"> I also conducted a simple test using 3.2.2, and it worked normally to close the cdc task. At the same time, I also tested it with version 3.2.2 and found that the cdc task couldn't be closed normally. I discovered that in version **3.2.2, ds stops the task through `kill -9`.** When -9 kill is used, only the parent process may be killed. Due to the limited propagation of the SIGKILL signal, the cdc job child process may become an orphan process **After 3.3.x, tasks are stopped using `kill -15`**, thus the SIGTERM signal will be passed to the entire process group. -- 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]
