You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Kirk True (Jira)" <ji...@apache.org> on 2024/09/11 00:33:00 UTC
[jira] [Commented] (KAFKA-17518) AsyncKafkaConsumer cannot reliably leave group when closed with small timeout
[ https://issues.apache.org/jira/browse/KAFKA-17518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880817#comment-17880817 ]
Kirk True commented on KAFKA-17518:
-----------------------------------
This issue was found during [review|[https://github.com/apache/kafka/pull/16686]] and testing for KAFKA-16985.
> AsyncKafkaConsumer cannot reliably leave group when closed with small timeout
> -----------------------------------------------------------------------------
>
> Key: KAFKA-17518
> URL: https://issues.apache.org/jira/browse/KAFKA-17518
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Affects Versions: 3.9.0
> Reporter: Kirk True
> Priority: Major
> Labels: consumer-threading-refactor, kip-848-client-support
>
> If {{close()}} is called with a short timeout (e.g. 0 ms), the process cannot complete, leading to the consumer remaining in the consumer group.
> On {{{}close(){}}}, the consumer attempts to unsubscribe and leave the consumer group. This process requires hops back and forth between the application and background threads to call the {{{}ConsumerRebalanceListener{}}}. Those hops add a nonzero amount of time to the close step.
> The events used to communicate between the application and background threads are based on the timeout provided by the user. If the timeout is not sufficient, the events will expire, and the process will be left incomplete.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)