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/03/10 14:11:09 UTC
[GitHub] [dolphinscheduler] guoshupei commented on issue #8810: [Bug] [Master] Process Instance state does not change correctly and may cause Memory Leak
guoshupei commented on issue #8810:
URL: https://github.com/apache/dolphinscheduler/issues/8810#issuecomment-1064104565
ok. @caishunfeng I use `try catch`, first, ensure `WorkflowExecuteThread` can be deleted and continue to handle events; second, print exception message to locate problem
For now, I'm just printing out exception messages so you can locate problem.
The following is my personal opinion. I have studied and found the errors are mainly in the `notifyProcessChanged` method. If `try catch` is used, although the cause of the error is located, the solution cost is high, such as `repeat running` to solve the problem, which wastes time and resources.
if transfer to `command`, insert a command to resolve
--
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