You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
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
The text was updated successfully, but these errors were encountered: