[
https://issues.apache.org/jira/browse/KAFKA-19062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shivsundar R updated KAFKA-19062:
---------------------------------
Description:
After
[https://github.com/apache/kafka/commit/66363160c5e4460d9be27afa21c103a56f7428bc]
, we handle the close timeout in AsyncKafkaConsumer by taking the minimum of
user given timeout and the default request timeout config.
These changes need to applied to ShareConsumers as well.
was:
After
[https://github.com/apache/kafka/commit/66363160c5e4460d9be27afa21c103a56f7428bc]
, we handle the close timeout in AsyncKafkaConsumer by taking the minimum of
user given timeout and the default API request timeout. The time for processing
callbacks is not counted as part of the close timeout handling.
These changes need to applied to ShareConsumers as well.
> ShareConsumer should align handling of close timeout with async consumer.
> -------------------------------------------------------------------------
>
> Key: KAFKA-19062
> URL: https://issues.apache.org/jira/browse/KAFKA-19062
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Shivsundar R
> Assignee: Shivsundar R
> Priority: Major
>
> After
> [https://github.com/apache/kafka/commit/66363160c5e4460d9be27afa21c103a56f7428bc]
> , we handle the close timeout in AsyncKafkaConsumer by taking the minimum of
> user given timeout and the default request timeout config.
> These changes need to applied to ShareConsumers as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
