[
https://issues.apache.org/jira/browse/KAFKA-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778780#comment-16778780
]
Guozhang Wang commented on KAFKA-7996:
--------------------------------------
If a KafkaStreams instance is in ERROR state, one should call close() on it to
make sure all the corresponding resources (state directory, threads, locks,
etc) are reclaimed before starting a new one. The cleanup() call will just wipe
out the local state stores, and is usually used if you do not want to have
another instance on this host and just want to free-up its state store
footprint on disks.
> 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)
