This repository was archived by the owner on Jul 11, 2025. It is now read-only.
Change loglevel of cancelled errors to info #190
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
copy of PR 2404 on base repo
See dpkp#1583
When closing the connection on purpose by calling consumer.close(), each ongoing Fetch request will be cancelled, by setting a Cancelled KafkaException on that particular request.
Due to the error callback on this object, which is nothing else except a logging statement, the cancellation will be logged with level ERROR, instead as INFO, while it is not actually an error, but a way of stopping the ongoing request