Kris20030907 opened a new issue, #10193: URL: https://github.com/apache/rocketmq/issues/10193
### 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 MacOS ### RocketMQ version develop ### JDK Version jdk8 ### Describe the Bug Minimum read offset boundary issue. `TieredMessageStore#getMinOffsetInQueue` may return an incorrect result when the local store does not have a valid min offset but tiered storage still has readable data. At present, the method merges the min offset from the next store and tiered store like this: - return local min offset if tiered min offset is invalid - otherwise return `Math.min(localMinOffset, tieredMinOffset)` The problem is that the local store may return `-1` as a sentinel value when no valid local min offset is available. In that case, `-1` is not a real queue offset and should not participate in the final comparison. ### Steps to Reproduce null ### What Did You Expect to See? need to return when the tiered store offset is valid and local store don't have valid offset ### What Did You See Instead? The effective offset of a tiered store will be ignored, and the method returns -1 ### 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]
