Skip to content

KAFKA-19463: nextFetchOffset does not take ongoing state transition into account #20080

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 2 commits into
base: trunk
Choose a base branch
from
Open

KAFKA-19463: nextFetchOffset does not take ongoing state transition into account #20080

wants to merge 2 commits into from
+176 −2

Conversation

adixitconfluent
Copy link
Contributor

About

nextFetchOffset function in SharePartition updates the fetch offsets without considering batches/offsets which might be undergoing state transition. This can cause problems in updating to the right fetch offset.

Testing

The new code added has been tested with the help of unit tests.
@github-actions github-actions bot added triage PRs from the community core Kafka Broker KIP-932 Queues for Kafka labels Jul 1, 2025
@apoorvmittal10 apoorvmittal10 added ci-approved and removed triage PRs from the community labels Jul 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-approved core Kafka Broker KIP-932 Queues for Kafka
2 participants
@adixitconfluent @apoorvmittal10