Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Avoid dispatch tasks too much cause submit dispatch task failed #7093

Closed
3 tasks done
lizhimins opened this issue Jul 28, 2023 · 0 comments · Fixed by #7094
Closed
3 tasks done

[Bug] Avoid dispatch tasks too much cause submit dispatch task failed #7093

lizhimins opened this issue Jul 28, 2023 · 0 comments · Fixed by #7094

Comments

@lizhimins
Copy link
Member

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

RongtongJin pushed a commit that referenced this issue Aug 1, 2023
#7094)

* Avoid dispatch tasks too much cause dispatch task failed

* set schedule task async
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant