njnu-seafish commented on PR #17320:
URL:
https://github.com/apache/dolphinscheduler/pull/17320#issuecomment-3036697134
> I've tested this issue #17316 base on your reproduction steps in macos and
ubuntu 24.04 and found this issue does not exist, please describe the specific
reproduction environment. @njnu-seafish
After fixing the bug according to the code above, the log of the task
instance is as follows.
`
Final Shell file is:
****************************** Script Content
*****************************************************************
#!/bin/bash
BASEDIR=$(cd `dirname $0`; pwd)
cd $BASEDIR
source /usr/local/dolphinscheduler/bin/env/dolphinscheduler_env.sh
echo ${JAVE_HOME}
sleep 10m
****************************** Script Content
*****************************************************************
Executing shell command : sudo -u dolphinscheduler -i
/data01/dolphinscheduler/exec/process/130/130.sh
process start, process id is: 643464
Begin killing task instance, processId: 643464
prepare to parse pid, raw pid string:
sudo(643464)---130.sh(643479)---sleep(643559)
Kill command: kill -s SIGINT 643464 643479 643559, trying to terminate
process
Kill command: sudo -u dolphinscheduler -i kill -s SIGINT 643464 643479
643559, kill failed, the process: 643464 is still running
Kill command: kill -s SIGTERM 643464 643479 643559, trying to terminate
process
Kill command: sudo -u dolphinscheduler -i kill -s SIGTERM 643464 643479
643559, kill succeeded
Successfully killed process tree using SIGTERM, processId: 643464
Process tree for task: 130 is killed or already finished, pid: 643464
`
--
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]
