humkum opened a new issue, #10176: URL: https://github.com/apache/rocketmq/issues/10176
### 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 Euler ### RocketMQ version develop ### JDK Version JDK8 ### Describe the Bug In DefaultLitePullConsumerImpl.PullTaskImpl.run(), when nextPullOffset() is called, it may return a negative value (typically -1). This happens in the fetchConsumeOffset() → computePullFromWhereWithException() path. If the returned offset is -1, it was directly passed to the broker's pull() method, which could cause the consumer to reset its consumption position to minOffset, re-consuming already processed messages. ### Steps to Reproduce Try to cause an OutOfMemory ERROR after LitePullConsumer firstly start ### What Did You Expect to See? The consumer consume message continuely. ### What Did You See Instead? The consumer's consume offset was reset to min. ### 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]
