rickchengx commented on PR #11668: URL: https://github.com/apache/dolphinscheduler/pull/11668#issuecomment-1229971145
Hi, @fengjian1129 Could you please show the `worker log` (especially the log related to `TaskKillProcessor`) when you successfully stop the `sql` task as below:  And for reference, i think it cannot stop the sql task correctly is because the `null pointer` exception in #11175 Here is the log: ``` [INFO] 2022-08-29 07:15:09.412 +0000 org.apache.dolphinscheduler.server.worker.processor.TaskKillProcessor:[90] - [WorkflowInstance-0][TaskInstance-0] - task kill command : TaskKillRequestCommand(taskInstanceId=27) [INFO] 2022-08-29 07:15:09.413 +0000 org.apache.dolphinscheduler.server.worker.processor.TaskKillProcessor:[177] - [WorkflowInstance-0][TaskInstance-0] - kill task by cancelApplication, task id:27 [ERROR] 2022-08-29 07:15:09.418 +0000 org.apache.dolphinscheduler.remote.handler.NettyServerHandler:[131] - [WorkflowInstance-0][TaskInstance-0] - process msg Command [type=TASK_KILL_REQUEST, opaque=80, bodyLen=21] error java.lang.NullPointerException: null at org.apache.dolphinscheduler.server.worker.processor.TaskKillProcessor.sendTaskKillResponseCommand(TaskKillProcessor.java:127) at org.apache.dolphinscheduler.server.worker.processor.TaskKillProcessor.process(TaskKillProcessor.java:106) at org.apache.dolphinscheduler.remote.handler.NettyServerHandler.lambda$processReceived$0(NettyServerHandler.java:129) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) ``` -- 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]
