[ https://issues.apache.org/jira/browse/KAFKA-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798528#comment-16798528 ]
Matthias J. Sax commented on KAFKA-7996: ---------------------------------------- How would this config and `KafakStreams#close(timeout)` relate to each other? Not saying we should not add a config, just want to understand it better. What is the advantage compared to alternatives? Could we use `KafkaStreams#close(timeout)` and pass it to the internal clients instead (advantages/disadvantages)? Maybe those question could also be part of a KIP discussion. I think, it still don't fully understand the tradeoffs yet for different approaches. > 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)