Skip to content

KAFKA-7138: Add DLQ name and replication factor to Connect configuration #20782

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: trunk
Choose a base branch
from
Open

KAFKA-7138: Add DLQ name and replication factor to Connect configuration #20782

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
11e1b52
Add dlq name and replication factor to connect configuration file
zheguang Oct 28, 2025
75d8ea3
Enable context headers in dlq messages
zheguang Oct 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions config/connect-distributed.properties
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,16 @@ status.storage.topic=connect-status
status.storage.replication.factor=1
#status.storage.partitions=5

# Topic to use for storing messages that result in an error when processed by this sink connector, or its transformations or converters.
# Kafka Connect will attempt to create the topic automatically when needed, but you can always manually create
# the topic before starting Kafka Connect if a specific topic configuration is needed.
# Most users will want to use the built-in default replication factor of 3 or in some cases even specify a larger value.
# Since this means there must be at least as many brokers as the maximum replication factor used, we'd like to be able
# to run this example on a single-broker cluster and so here we instead set the replication factor to 1.
errors.deadletterqueue.topic.name=connect-dlq
errors.deadletterqueue.topic.replication.factor=1
errors.deadletterqueue.context.headers.enable=true

# Flush much faster than normal, which is useful for testing/debugging
offset.flush.interval.ms=10000

Expand Down