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] wrong result of searchOffset in tiered storage #7345

Closed
3 tasks done
yuz10 opened this issue Sep 11, 2023 · 0 comments · Fixed by #7346
Closed
3 tasks done

[Bug] wrong result of searchOffset in tiered storage #7345

yuz10 opened this issue Sep 11, 2023 · 0 comments · Fixed by #7346

Comments

@yuz10
Copy link
Member

yuz10 commented Sep 11, 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

Ubuntu

RocketMQ version

5.1.0

JDK Version

1.8.0

Describe the Bug

There are 3 segments in fileSegmentList, TieredFlatFile.getFileByTime(timestamp=0, boundaryType=LOWER) should return the first segment, but now returns the last segment.

image

Steps to Reproduce

  1. start broker with tiered storage
  2. send some messages.
  3. use consumer.searchOffset to search offset with parameter timestamp=0, boundaryType=LOWER

What Did You Expect to See?

searchOffset should return min offset.

What Did You See Instead?

searchOffset not returns min offset.

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