[
https://issues.apache.org/jira/browse/KAFKA-19891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038887#comment-18038887
]
Shivsundar R commented on KAFKA-19891:
--------------------------------------
Right Im not sure too if the user should be made aware of these errors. I can
take this up and raise a fix for this? I see ClassicKafkaConsumer logs at WARN
level for timeouts and handles error responses(including logging) even during
close.
Here AsyncConsumer ignores the responses and just logs the error, so maybe we
can warn for timeout exception only?
> AsyncKafkaConsumer logs "Unexpected exception" for timeouts during close
> ------------------------------------------------------------------------
>
> Key: KAFKA-19891
> URL: https://issues.apache.org/jira/browse/KAFKA-19891
> Project: Kafka
> Issue Type: Bug
> Reporter: Lucas Brutschy
> Priority: Minor
>
> The new consumer (in share, consumer and streams groups) log "unexpected
> exception" at error log level when hitting a timeout during consumer close:
> [https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/consumer/internals/AbstractHeartbeatRequestManager.java#L318]
> [https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/consumer/internals/StreamsGroupHeartbeatRequestManager.java#L489]
> This is confusing, since this is not really unexpected, and should probably
> be logged at warn level at most.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
