github-actions[bot] commented on issue #13390:
URL: 
https://github.com/apache/dolphinscheduler/issues/13390#issuecomment-1379987872

   ### 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
   
   Recently, the company researched dolphinscheduler again. When I was using 
it, I often encountered that the task at the beginning could not be finished, 
and then I stopped it manually. It would show that it was ready to stop on the 
workflow instance, but it couldn't stop.
   
   
   ### What you expected to happen
   
   Query the log of the background master, the log is repeated as follows
   
![image](https://user-images.githubusercontent.com/46471288/212018998-e19f73ff-40d7-4de5-9fcf-5089506f6ff4.png)
   And the log volume is increasing frequently, and the repeated logs cause the 
disk usage to soar
   
![image](https://user-images.githubusercontent.com/46471288/212018750-c002250d-078a-47ba-b257-14b131188da1.png)
   I encountered this when I was using 3.1.1 before, and now I have upgraded to 
3.1.3, and I still have this problem
   
   ### How to reproduce
   
   I need to manually update the status field of the t_ds_process_instance 
table to stop,
   
![image](https://user-images.githubusercontent.com/46471288/212019271-054a9b57-ccf0-41cf-8f9b-5242bf3be2e6.png)
   Then restart the cluster manually to solve this problem. This brings us a 
serious challenge to online dolphinscheduler
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   dev
   
   ### 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