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] When the broker scales up, the PopConsumer that uses Max to pull may have message loss #7117

Closed
3 tasks done
xdkxlk opened this issue Aug 4, 2023 · 0 comments · Fixed by #7118
Closed
3 tasks done

Comments

@xdkxlk
Copy link
Contributor

xdkxlk commented Aug 4, 2023

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

  1. Pop message from broker with the Max consumeInitMode
  2. Scale up a new broker
  3. Since ConsumeInitMode is Max, new messages sent to new brokers may be skipped

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

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