lizhimins opened a new issue, #9813: URL: https://github.com/apache/rocketmq/issues/9813
### Before Creating the Bug Report - [x] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [x] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate. - [x] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Runtime platform environment Linux 5.19 ### RocketMQ version [5.x-5.3.3) ### JDK Version JDK17 ### Describe the Bug The asynchronous chain directly calls the synchronous getMessageFromCache, which internally goes through FlatMessageFile.getConsumeQueueMinOffset → FlatCommitLogFile.getMinOffsetFromFile → getMinOffsetFromFileAsync().join, thus blocking and waiting in the callback thread, causing thread pool starvation. ### Steps to Reproduce The asynchronous chain directly calls the synchronous getMessageFromCache, which internally goes through FlatMessageFile.getConsumeQueueMinOffset → FlatCommitLogFile.getMinOffsetFromFile → getMinOffsetFromFileAsync().join, thus blocking and waiting in the callback thread, causing thread pool starvation. ### What Did You Expect to See? no thread block ### What Did You See Instead? thread pool starvation ### Additional Context _No response_ -- 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]
