lizhimins opened a new issue, #9626: URL: https://github.com/apache/rocketmq/issues/9626
### 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 5.10 ### RocketMQ version 5.2-5.3.3 ### JDK Version JDK11 ### Describe the Bug It is a concurrency issue: when thread A tries to remove data from the cache, the records have not yet been flushed to disk. If thread B attempts to fetch the minimum offset from the cache and commit it at the same time, any unflushed records may be lost in the event of a crash. ### Steps to Reproduce It is a concurrency issue: when thread A tries to remove data from the cache, the records have not yet been flushed to disk. If thread B attempts to fetch the minimum offset from the cache and commit it at the same time, any unflushed records may be lost in the event of a crash. ### What Did You Expect to See? Prevent premature offset commit before consumer record flush ### What Did You See Instead? consumer record flush then commit min offset ### 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]
