[
https://issues.apache.org/jira/browse/KAFKA-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784092#comment-16784092
]
Matthias J. Sax commented on KAFKA-7996:
----------------------------------------
[~dongjin] Consumer also has config
`ConsumerConfig#DEFAULT_API_TIMEOUT_MS_CONFIG`? Not sure why it does not use it
in close() thought. \cc [~hachikuji] is this a bug?
I am not sure what the overall approach to handle timeouts is atm, and if we
should do (2) or not – however, we should take existing
DEFAULT_API_TIMEOUT_MS_CONFIG into account if we do this. I seems that if we
add a config to Streams, we can follow this pass and also add it to producer
and admin client.
I hope [~guozhang] and [~hachikuji] can provide some input. Also cc [~Yohan123]
who implemented KIP-266 and [~vvcephei] who help to shape the KIP.
> KafkaStreams does not pass timeout when closing Producer
> --------------------------------------------------------
>
> Key: KAFKA-7996
> URL: https://issues.apache.org/jira/browse/KAFKA-7996
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 2.1.0
> Reporter: Patrik Kleindl
> Assignee: Lee Dongjin
> Priority: Major
> Labels: needs-kip
>
> [https://confluentcommunity.slack.com/messages/C48AHTCUQ/convo/C48AHTCUQ-1550831721.026100/]
> We are running 2.1 and have a case where the shutdown of a streams
> application takes several minutes
> I noticed that although we call streams.close with a timeout of 30 seconds
> the log says
> [Producer
> clientId=…-8be49feb-8a2e-4088-bdd7-3c197f6107bb-StreamThread-1-producer]
> Closing the Kafka producer with timeoutMillis = 9223372036854775807 ms.
> Matthias J Sax [vor 3 Tagen]
> I just checked the code, and yes, we don't provide a timeout for the producer
> on close()...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
