You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2022/12/26 06:53:28 UTC

[GitHub] [dolphinscheduler] KEN-LJQ commented on issue #10012: [Bug] [Master] After the task is paused, it cannot be started again

KEN-LJQ commented on issue #10012:
URL: https://github.com/apache/dolphinscheduler/issues/10012#issuecomment-1364939815

   @SbloodyS 
   Hi, we met this problem on version 2.0.7, when we pause a process instance, it stuck and all operation are unavailable.
   The way to reproduce is:
   1. Create process with one task, and this task suppose to execute failed like `selet 1`, then set retry 3 times with interval.
   2. Run this process. And at this moment, task instance will be failure to wait for retry, and process instance state is running
   3. Click pause buttom
   4. Then all operation buttom are unavailable unless you restart master
   
   And we check all log with master and worker, no error log show, and only have this
   ```
   2022-12-26 14:45:38.279  INFO 3864 --- [ool-10-thread-6] o.a.d.s.m.processor.StateEventProcessor  : received command : State Event :key: 46-0-46-0 type: PROCESS_STATE_CHANGE executeStatus: READY_PAUSE task instance id: 0 process instance id: 46 context: null
   2022-12-26 14:45:38.649  INFO 3864 --- [tServiceStarted] o.a.d.s.m.runner.EventExecuteService     : handle process instance : 46 , events count:1
   2022-12-26 14:45:38.649  INFO 3864 --- [tServiceStarted] o.a.d.s.m.runner.EventExecuteService     : already exists handler process size:0
   2022-12-26 14:45:38.650  INFO 3864 --- [rEventExecution] o.a.d.s.m.runner.WorkflowExecuteThread   : process event: State Event :key: 46-0-46-0 type: PROCESS_STATE_CHANGE executeStatus: READY_PAUSE task instance id: 0 process instance id: 46 context: null
   2022-12-26 14:45:38.650  INFO 3864 --- [rEventExecution] o.a.d.s.m.runner.WorkflowExecuteThread   : process:46 state RUNNING_EXECUTION change to READY_PAUSE
   ```
   
   It seem like this process instance waiting for next event to trigger to change its state, but this nerver happen.
   Do you know anything about this?


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org