[
https://issues.apache.org/jira/browse/KAFKA-9830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantine Karantasis updated KAFKA-9830:
------------------------------------------
Fix Version/s: 2.6.0
> DeadLetterQueueReporter leaks KafkaProducer instance
> ----------------------------------------------------
>
> Key: KAFKA-9830
> URL: https://issues.apache.org/jira/browse/KAFKA-9830
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 2.0.0
> Reporter: Greg Harris
> Assignee: Greg Harris
> Priority: Major
> Fix For: 2.6.0, 2.5.1
>
>
> The DeadLetterQueueReporter (introduced by KAFKA-6738) creates a
> KafkaProducer to report errors to Kafka, but does not clean up the producer,
> leaving many idle network threads open after tasks are stopped.
> Reproduction steps:
> Start a task that has a non-empty DLQ topic name
> Stop the task
> Observe the list of running threads
> Expected result:
> There is no thread related to the stopped task's DLQ left running
> Actual result:
> There is a thread named something like kafka-producer-network-thread |
> connector-dlq-producer-task-0" #1234 left running
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
