FantasticMM opened a new issue #6332: URL: https://github.com/apache/dolphinscheduler/issues/6332
### 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 java.lang.IllegalStateException: Queue full at java.util.AbstractQueue.add(AbstractQueue.java:98) at org.apache.dolphinscheduler.server.worker.task.AbstractCommandExecutor.lambda$parseProcessOutput$3(AbstractCommandExecutor.java:356) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) is this because AbstractCommandExecutor.clear() method didn't clear queue? I notice since 1.3.7 logBuffer become a LinkedBlockingQueue, and in AbstractCommandExecutor.clear() miss logBuffer.clear(). I'll take two photos for compare 1.3.6 and 1.3.8 1.3.6  1.3.8  ### What you expected to happen I think there miss a line of code logBuffer.clear() ### How to reproduce I do not konw actually , my colleague just run task normally, and failed ### Anything else _No response_ ### 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]
