[
https://issues.apache.org/jira/browse/KAFKA-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542164#comment-16542164
]
Robin Moffatt commented on KAFKA-7138:
--------------------------------------
{quote}as with the other replication factor properties, set them to 1 in the
properties files and include a comment that they should be changed to at least
'3' for production usage.
{quote}
I would +1 this approach, as it retains consistency with what we currently do.
> 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
> 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)
