[
https://issues.apache.org/jira/browse/KAFKA-19891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039528#comment-18039528
]
Anton Vasanth commented on KAFKA-19891:
---------------------------------------
Hi all,
I'd like to help with this issue.
Since the correct log behavior is still being discussed, my plan is to start by
investigating the exact scenarios where the “Unexpected ” log is emitted in
{{AsyncKafkaConsumer}} and the event loop.
I will map out:
# The state transitions that trigger this log
# Which transitions are valid vs. truly unexpected
After gathering that information, I’ll summarize my findings here so the
correct approach can be decided together.
If nobody is actively working on this, could you please assign the issue to me?
> 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
> Components: clients, consumer
> 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)
