xdkxlk opened a new issue, #7117: URL: https://github.com/apache/rocketmq/issues/7117
### 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 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_ -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
