Reset offset to :earliest_offset whenever OffsetOutOfRange happens#1
Closed
alexcastano wants to merge 1 commit intoqltysh-archive:masterfrom
alexcastano:patch-1
Closed
Reset offset to :earliest_offset whenever OffsetOutOfRange happens#1alexcastano wants to merge 1 commit intoqltysh-archive:masterfrom alexcastano:patch-1
alexcastano wants to merge 1 commit intoqltysh-archive:masterfrom
alexcastano:patch-1
Conversation
bpot#102 OffsetOutOfRange error can also happen when the returned offset is a positive number but corresponding messages started from the offset were retentioned
|
Hey @alexcastano, Thanks for the PR! This is probably a change best made upstream. I see you already have a PR open on bpot/poseidon, so hopefully that's addressed and we'll update our fork later on. Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
bpot#102
OffsetOutOfRange error can also happen when the returned offset is
a positive number but corresponding messages started from the offset
were retentioned