[
https://issues.apache.org/jira/browse/KAFKA-17518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883212#comment-17883212
]
TengYao Chi commented on KAFKA-17518:
-------------------------------------
Hi [~kirktrue] and [~lianetm]
I'm now reading the context of this issue.
We are trying to align the behavior between classic consumer and async
consumer. Regarding the
[discussion|https://github.com/apache/kafka/pull/16686/files/fe5464bc6248b8cfb9ff5a43e3adb5fd912aae2f#r1747345639]
in PR-16686, are we decide to have a new application event
(GenerateLeaveRequestEvent) to handle this issue or it just a proposal ?
Thanks.
> 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
> Assignee: TengYao Chi
> 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)
