albertzzas opened a new issue, #13940:
URL: https://github.com/apache/dolphinscheduler/issues/13940

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   We use work process with 'sub_process' task to control the entry of every 
layer, such ods,ads.
   If trigger the button 'STOP' when parent process is running, then work 
process is supposed to change to 'STOP'.
   But it doesn't work in 3.1.5 , still hang with status 'PREPARE TO STOP' and 
child process is RUNNING.
   
   Worker LOG is fine
   Master LOG:
   - worker worker in work group default have not received the heartbeat
   - The task execution status code: 5 is invalidated
   
   [ERROR] 2023-04-17 01:27:33.890 -0500 TaskLogLogger-class 
org.apache.dolphinscheduler.server.master.runner.task.SubTaskProcessor:[91] - 
[WorkflowInstance-22595][TaskInstance-246877] - work flow 22595 sub task 246877 
exceptions
   java.lang.IllegalArgumentException: The task execution status code: 5 is 
invalidated
           at 
org.apache.dolphinscheduler.plugin.task.api.enums.TaskExecutionStatus.of(TaskExecutionStatus.java:60)
           at 
org.apache.dolphinscheduler.server.master.runner.task.SubTaskProcessor.updateTaskState(SubTaskProcessor.java:133)
           at 
org.apache.dolphinscheduler.server.master.runner.task.SubTaskProcessor.runTask(SubTaskProcessor.java:88)
           at 
org.apache.dolphinscheduler.server.master.runner.task.BaseTaskProcessor.run(BaseTaskProcessor.java:237)
           at 
org.apache.dolphinscheduler.server.master.runner.task.BaseTaskProcessor.action(BaseTaskProcessor.java:209)
           at 
org.apache.dolphinscheduler.server.master.event.TaskStateEventHandler.handleStateEvent(TaskStateEventHandler.java:88)
           at 
org.apache.dolphinscheduler.server.master.runner.WorkflowExecuteRunnable.handleEvents(WorkflowExecuteRunnable.java:288)
           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)
   [WARN] 2023-04-17 01:27:34.258 -0500 
org.apache.dolphinscheduler.server.master.dispatch.host.LowerWeightHostManager:[132]
 - [WorkflowInstance-0][TaskInstance-0] - worker worker in work group default 
have not received the heartbeat
   [WARN] 2023-04-17 01:27:34.258 -0500 
org.apache.dolphinscheduler.server.master.dispatch.host.LowerWeightHostManager:[132]
 - [WorkflowInstance-0][TaskInstance-0] - worker worker in work group default 
have not received the heartbeat
   
   
   ### What you expected to happen
   
   if trigger the button 'STOP' when process is running, then work process is 
supposed to change to 'STOP'.
   We use this function all the time via 1.3.6
   
   ### How to reproduce
   
   Test1:OK
   Process Action: 'STOP'
   Work process: doesn't use sub_process task 
   Task status:'KILL'
   Result:'STOP' 
   
   -----------------------------
   Test2: Failed
   Process  Action: 'STOP'
   Work process: use 'sub_process' task
   Task status:'KILL'
   Parent process result: 'PREPARE TO STOP' ,state code: 4 
   Child process result:'RUNNING' ,state code :1
   
   
   ### Anything else
   
   ENV and others
   Version: git clone -b 3.1.5  https://github.com/apache/dolphinscheduler.git
   Meta DB: Upgraded Mysql db via DS tools from 1.3.6->2.0.6->3.1.5
   ZK version:<zookeeper.version>3.4.6</zookeeper.version>
   Workgroup exists already , infor can be found in 
t_ds_task_instance.work_group
   
   
   ### Version
   
   3.1.x
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]

Reply via email to