Fix stale fetch detection across poll boundaries#3053
Open
platinumhamburg wants to merge 1 commit intoapache:mainfrom
Open
Fix stale fetch detection across poll boundaries#3053platinumhamburg wants to merge 1 commit intoapache:mainfrom
platinumhamburg wants to merge 1 commit intoapache:mainfrom
Conversation
Use nextFetchOffset for collector stale checks so a single CompletedFetch can be consumed across multiple polls without being drained as obsolete. Add focused unit and filter IT regression tests proving the pre-fix failure and post-fix correctness in single- and multi-bucket scenarios.
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
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.
Use nextFetchOffset for collector stale checks so a single CompletedFetch can be consumed across multiple polls without being drained as obsolete. Add focused unit and filter IT regression tests proving the pre-fix failure and post-fix correctness in single- and multi-bucket scenarios.
Purpose
Linked issue: close #3052
Brief change log
Tests
API and Format
Documentation