-
Notifications
You must be signed in to change notification settings - Fork 14.7k
MINOR: fix incorrect offset reset logging #20558
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
Conversation
This issue was introduced with 6cdb8c3 in AK 4.0.0 release. We should cherry-pick the fix accordingly. |
streams/src/main/java/org/apache/kafka/streams/processor/internals/StreamThread.java
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haha, I had the same PR locally.
Can I hijack this PR for a different change? We don't seem to log at all when we receive a InvalidOffsetException
from Consumer.poll
- so it's not clear where we call this function from the logs. So I would like to have a
} catch (final InvalidOffsetException e) {
log.info("Found no valid offset for {} partitions, resetting.", e.partitions().size());
resetOffsets(e.partitions(), e);
}
in StreamThread.pollRequests
. Maybe you can add this here, otherwise I will push a separate PR
We need to only pass in the reset strategy, as the `logMessage` parameter was removed. Reviewers: Chia-Ping Tsai <chia7712@gmail.com>, Lucas Brutschy <lbrutschy@confluent.io>
Thanks for merging Lucas. -- Also cherry-picked to @clolov -- if you do a new RC for 4.0.1, and feel like it, might also be nice to cherry-pick to |
We need to only pass in the reset strategy, as the `logMessage` parameter was removed. Reviewers: Chia-Ping Tsai <chia7712@gmail.com>, Lucas Brutschy <lbrutschy@confluent.io>
We need to only pass in the reset strategy, as the
logMessage
parameter was removed.
Reviewers: Chia-Ping Tsai chia7712@gmail.com, Lucas Brutschy
lbrutschy@confluent.io