lizhimins opened a new issue, #7093: URL: https://github.com/apache/rocketmq/issues/7093
### 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 MacOS JDK11 ### RocketMQ version develop latest ### JDK Version JDK11 ### Describe the Bug When the broker crashes abnormally, it will re-dispatch the latest approximately 3G messages. At this time, due to the fact that the dispatch thread of tiered storage is not fast enough to handle them, it can cause the length limit of the queue to be exceeded. ### Steps to Reproduce No ### What Did You Expect to See? The logic of immediately re-dispatching after removing the dispatch has been removed, and normal startup is now possible. ### What Did You See Instead? The logic of immediately re-dispatching after removing the dispatch has been removed, and normal startup is now possible. ### 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: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
