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

[v22.3.x] cloud_storage: Handle overlapping segments #10693

Merged

Conversation

VladLazar
Copy link
Contributor

Manual backport of #10683, fixes #10686

(cherry picked from commit 2712b02)

Backports Required

  • none - not a bug fix
  • none - this is a backport
  • none - issue does not exist in previous branches
  • none - papercut/not impactful enough to backport
  • v23.1.x
  • v22.3.x
  • v22.2.x

Release Notes

  • none

Bug Fixes

  • Fixes overlapping segments when consuming in tiered storage read path.

jcsp and others added 2 commits May 11, 2023 12:49
We already silenced these in the most common case
where they came after consuming some records: also
silence them in the case where the error status
is set when we enter ::consume

(cherry picked from commit 26fd35c)
When a reader appears stuck because it cannot make progress through its
current segment, one reason for this may be that the segment ends
earlier than the manifest entry indicates, and the next offset to be
read from lies within the next segment. This change catches a stuck
reader exception, and if the reader is not at the logical end but the
next offset lies in the next segment, the reader is forced to an EOF
state. Then we try to reset the reader to point to the next segment,
which should allow the read to progress.

(cherry picked from commit 2712b02)
@piyushredpanda
Copy link
Contributor

Unit tests have passed; merging.

@piyushredpanda piyushredpanda merged commit a296897 into redpanda-data:v22.3.x May 11, 2023
22 of 25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants