[
https://issues.apache.org/jira/browse/KAFKA-18645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17924088#comment-17924088
]
Lianet Magrans commented on KAFKA-18645:
----------------------------------------
Merged to trunk and cherry-picked to 4.0 (single PR including this issue and
the blocker subtask)
> New consumer should align close timeout handling with classic consumer
> ----------------------------------------------------------------------
>
> Key: KAFKA-18645
> URL: https://issues.apache.org/jira/browse/KAFKA-18645
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Reporter: TengYao Chi
> Assignee: TengYao Chi
> Priority: Blocker
> Labels: kip-848-client-support
> Fix For: 4.0.0
>
>
> see discussion:
> [https://github.com/apache/kafka/pull/18590#issuecomment-2612654505]
> In the classic consumer, the timeout respects {{request.timeout.ms.}}
> However, in the async consumer, this logic is either missing or only applies
> to individual requests. Unlike the classic consumer, where
> {{request.timeout.ms}} works for the entire coordinator closing behavior, the
> async implementation handles timeouts differently.
> We should align the close timeout-handling to enable
> ConsumerBounceTest#testClose
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
