[
https://issues.apache.org/jira/browse/FLINK-9287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463519#comment-16463519
]
ASF GitHub Bot commented on FLINK-9287:
---------------------------------------
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/5952
Would filtering the thread count by thread name be helpful here?
Another possible approach to test this:
Maybe we can simply verify that the current transaction producer is closed
after the cleanup?
This would require making the `getCurrentTransaction()` method visible for
tests, though. We'll also need to have a `isClosed()` method on the
`FlinkKafkaProducer`.
> KafkaProducer011 seems to leak threads when not in exactly-once mode
> --------------------------------------------------------------------
>
> Key: FLINK-9287
> URL: https://issues.apache.org/jira/browse/FLINK-9287
> Project: Flink
> Issue Type: Bug
> Components: Kafka Connector
> Affects Versions: 1.5.0, 1.4.2
> Reporter: Christopher Ng
> Assignee: Piotr Nowojski
> Priority: Blocker
> Fix For: 1.5.0
>
>
> {{KafkaProducer011}} appears to be leaking {{kafka-producer-network-thread}}
> threads. As far as I can tell it happens when it is not in EXACTLY_ONCE
> mode, it seems that it creates a {{FlinkKafkaProducer}} but never closes it,
> even when the {{FlinkKafkaProducer011}} itself is closed.
> I observed this when running a local cluster and submitting and then
> cancelling a job, a lot of kafka threads were left alive afterwards.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
