lintingbin opened a new issue, #3582: URL: https://github.com/apache/amoro/issues/3582
### Search before asking - [x] I have searched in the [issues](https://github.com/apache/amoro/issues?q=is%3Aissue) and found no similar issues. ### What would you like to be improved? After updating to Amoro 0.8.0, the production environment's Amoro has many pending tasks, while the optimizer has a lot of idle resources. After investigation, it was found that the optimizer's pollTask sometimes takes a long time to execute. The root cause was traced to an issue with the TableOptimizingProcess.poll() function, likely because it uses the same lock as the committing function, resulting in prolonged wait times before returning. This also affects the execution of the OptimizingQueue.triggerAsyncPlanning function, causing delays in transitioning tasks from pending to planning status. ### How should we improve? _No response_ ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Subtasks _No response_ ### 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]
