[
https://issues.apache.org/jira/browse/KAFKA-19891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038842#comment-18038842
]
Shivsundar R commented on KAFKA-19891:
--------------------------------------
Hey [~lucasbru] , thanks for raising this.
I took a look and had a doubt, other than the timeout case, in cases of broker
disconnection or any auth exception, we will enter this part of the code on
close.
So there it would be nice to log at the error level right?
Maybe we can remove the word "unexpected" and have a better log line there?
What do you think?
> 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)
