[
https://issues.apache.org/jira/browse/KAFKA-19891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038865#comment-18038865
]
Lucas Brutschy commented on KAFKA-19891:
----------------------------------------
I'm not sure - if we timeout or disconnect during a close, does this really
indicate an error that the user should be aware of?
I agree that we could be more selective - maybe just remove "unexpected" and
reduce to WARN for timeout exception...
> 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)
