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

Posted to jira@kafka.apache.org by "Ismael Juma (Jira)" <ji...@apache.org> on 2020/01/25 21:34:00 UTC

[jira] [Commented] (KAFKA-8531) Change default replication factor config

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

Ismael Juma commented on KAFKA-8531:
------------------------------------

The default can only be used with new enough brokers. So Streams will have to fall back to the old behavior when talking to older brokers.

> Change default replication factor config
> ----------------------------------------
>
>                 Key: KAFKA-8531
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8531
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: 2.3.0
>            Reporter: Matthias J. Sax
>            Assignee: Matthias J. Sax
>            Priority: Minor
>              Labels: kip
>
> With KAFKA-8305, AdminClient allows to create topics based on the broker default replication factor.
> Kafka Streams sets `replication.factor` to 1 by default atm, to give a good out-of-the-box user experience. The problem is, that people may need to change the config if they push an application to production.
> We should change the default to `-1` to exploit the new AdminClient feature. This won't impact the out-of-the-box experience and may avoids the need to change the setting when pushing an application to production.
> We piggy-back this change to the original KIP: [https://cwiki.apache.org/confluence/display/KAFKA/KIP-464%3A+Defaults+for+AdminClient%23createTopic]



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