Skip to content

Fix stale fetch detection across poll boundaries#3053

Open
platinumhamburg wants to merge 1 commit intoapache:mainfrom
platinumhamburg:fix/stale-fetch-detection-cross-poll
Open

Fix stale fetch detection across poll boundaries#3053
platinumhamburg wants to merge 1 commit intoapache:mainfrom
platinumhamburg:fix/stale-fetch-detection-cross-poll

Conversation

@platinumhamburg
Copy link
Copy Markdown
Contributor

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

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.
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 this pull request may close these issues.

[client] LogFetchCollector uses immutable fetchOffset for staleness check, causing cross-poll CompletedFetch to be drained

1 participant