We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
linux
develop
No response
When the broker scales up, the PopConsumer that uses Max to pull may have message loss
When the broker scales up, the message will not be skipped
The new messages sent to new brokers may be skipped
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
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
linux
RocketMQ version
develop
JDK Version
No response
Describe the Bug
When the broker scales up, the PopConsumer that uses Max to pull may have message loss
Steps to Reproduce
What Did You Expect to See?
When the broker scales up, the message will not be skipped
What Did You See Instead?
The new messages sent to new brokers may be skipped
Additional Context
No response
The text was updated successfully, but these errors were encountered: