Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] [dolphinscheduler-master] Master logic task kill operation will never take effect. Although the TaskInstance state is set to KILL, the logic task will actually continue running in memory. #16895

Open
3 tasks done
tasier opened this issue Dec 12, 2024 · 0 comments
Labels
bug Something isn't working Waiting for reply Waiting for reply

Comments

@tasier
Copy link

tasier commented Dec 12, 2024

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

Although the kill master logic task operation is successful, the TaskInstance state is set to KILL, and there are no exceptions in the KILL operation, the logic task is actually still running and has not been truly killed.

What you expected to happen

Kill the master logic operation is successful and the logic task does not run again at the same time.

How to reproduce

step 1 create a logic task

  • Create a logic task such as a DEPENDENT task. The task content which is not important can be anything else. Following image is the task definition.
image

step 2 save and online the workflow definition

  • Save the workflow definition. After publishing the workflow definition, make the scheduler online. At last, manual start the workflow.
image

step3 stop the workflow

  • After the workflow is running, stop the workflow.
image image

step4 logic task is still running

  • Make a debug breakpoint at method org.apache.dolphinscheduler.server.master.runner.execute.AsyncMasterTaskDelayQueue#pollAsyncTask.
  • We can see that asyncTaskCheckDelayQueue still contains the stopped task. It will be running forever unless we redeploy the Dolphin-master service.
image

Anything else

No response

Version

3.2.2-release

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@tasier tasier added bug Something isn't working Waiting for reply Waiting for reply labels Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Waiting for reply Waiting for reply
Projects
None yet
Development

No branches or pull requests

1 participant