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

V21.11.x backport pr3280 #3343

Merged
merged 6 commits into from
Dec 22, 2021
Merged

Conversation

LenaAn
Copy link
Contributor

@LenaAn LenaAn commented Dec 22, 2021

Backport of #3280:

Cover letter

If segment in S3 was truncated, remote segment reader would be stuck in a cycle trying to read the data. Now it throws and exception instead.

Also fine-tuning misleading log messages from cloud_storage.

Fixes #3304

Release notes

Improvements

  • Gracefully handle a situation when segment in S3 is truncated. Before client would be stuck in a cycle trying to proceed, not client will get an error.

Elena Anyusheva added 6 commits December 22, 2021 17:03
Log messages about hydrating segments were misleading, fixing that.

(cherry picked from commit 918b728)
On end of stream the error from consuming header was not propagated,
fixing that.

Co-authored-by: Evgeny Lazin <evgeny@vectorized.io>
(cherry picked from commit 4b3d475)
Remote segment keeps bytes_consumed and if it's not progressing after
parser consume and it's not because the reader is overbudget, then
remote segment batch reader throws and exception.

(cherry picked from commit e2e2590)
Remote partition now propagates every error from reading from remote
segment. That error will be visible from client, but should  not terminate
client.

(cherry picked from commit 4eeb1cb)
@Lazin Lazin merged commit b6f1828 into redpanda-data:v21.11.x Dec 22, 2021
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

2 participants