Jave-Chen opened a new issue #1648: [BUG] fix "wait(...)" should be used instead of "Thread.sleep(...)" when a lock is held URL: https://github.com/apache/incubator-dolphinscheduler/issues/1648 *For better global communication, please give priority to using English description, thx! * **Describe the bug** If Thread.sleep(...) is called when the current thread holds a lock, it could lead to performance and scalability issues, or even worse to deadlocks because the execution of the thread holding the lock is frozen. It's better to call wait(...) on the monitor object to temporarily release the lock and allow other threads to run. see sonarcloud : https://sonarcloud.io/project/issues?id=apache-dolphinscheduler&issues=AW9PvkGGYzPBRjkobY32&open=AW9PvkGGYzPBRjkobY32
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
