You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Randall Hauch (Jira)" <ji...@apache.org> on 2020/06/10 22:33:00 UTC

[jira] [Updated] (KAFKA-9985) Sink connector consuming DLQ topic may exhaust broker

     [ https://issues.apache.org/jira/browse/KAFKA-9985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated KAFKA-9985:
---------------------------------
    Summary: Sink connector consuming DLQ topic may exhaust broker  (was: Sink connector may exhaust broker when writing in DLQ)

> Sink connector consuming DLQ topic may exhaust broker
> -----------------------------------------------------
>
>                 Key: KAFKA-9985
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9985
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 2.3.1, 2.5.0, 2.4.1
>            Reporter: Mario Molina
>            Assignee: Mario Molina
>            Priority: Major
>             Fix For: 2.6.0
>
>
> When a sink connector is configured with a DLQ and its topic is the same (or matches) as the topic in which the connector reads, the broker and/or connector might be exhausted in case the record send to the topic is invalid.
> Based on the broker/connect config, the connector might fail throwing a RecordTooLargeException previous to exhaust the broker/connector.



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