You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ray Chiang (JIRA)" <ji...@apache.org> on 2018/07/19 18:17:00 UTC
[jira] [Updated] (KAFKA-7138) Kafka Connect - Make
errors.deadletterqueue.topic.replication.factor default consistent
[ https://issues.apache.org/jira/browse/KAFKA-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ray Chiang updated KAFKA-7138:
------------------------------
Component/s: KafkaConnect
config
> Kafka Connect - Make errors.deadletterqueue.topic.replication.factor default consistent
> ---------------------------------------------------------------------------------------
>
> Key: KAFKA-7138
> URL: https://issues.apache.org/jira/browse/KAFKA-7138
> Project: Kafka
> Issue Type: Bug
> Components: config, KafkaConnect
> Reporter: Robin Moffatt
> Priority: Minor
>
> {{errors.deadletterqueue.topic.replication.factor}} defaults to RF 3
> The standard out of the box config files override the RF for {{offset.storage.replication.factor}} (and {{config}} and {{status}}) to 1
> To make the experience consistent for users (especially new users, running a single-node dev environment), the default RF in effect for {{errors.deadletterqueue.topic.replication.factor}} should also be 1.
> It would make it easier for devs getting started on single-node setups.
> For prod people should be actively configuring this stuff anyway, this would get included in that.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)