You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "rameshkrishnan muthusamy (Jira)" <ji...@apache.org> on 2020/05/26 19:12:00 UTC

[jira] [Commented] (KAFKA-10045) Kafka Connect Connection leak to Kafka Brokers when using dead letter queue

    [ https://issues.apache.org/jira/browse/KAFKA-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116987#comment-17116987 ] 

rameshkrishnan muthusamy commented on KAFKA-10045:
--------------------------------------------------

I am working on the fix for this issue , I will be sharing the design and PR for the same. 

> Kafka Connect Connection leak to Kafka Brokers when using dead letter queue
> ---------------------------------------------------------------------------
>
>                 Key: KAFKA-10045
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10045
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 2.1.1, 2.3.0, 2.4.1
>            Reporter: rameshkrishnan muthusamy
>            Priority: Major
>
> we are encountering a connection leak which accumulates over a period of time as the number of rebalances increase in Kafka Connect. The connection to the Kafka Broker for dead letter queue is never closed during rebalance. At the same time as part of rebalance a new connection is created for the dead letter queue kafka topic. This results in accumulation of open connections to Kafka Broker. This impacts the total no of connections and causes load on the kafka brokers over a period of time. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)