Table of Contents |
---|
Status
Current state: "Under Discussion"Accepted
Vote thread: Re: [VOTE} KIP-733: change Kafka Streams default replication factor config (there is no DISCUSS thread)Discussion thread: TODO
JIRA: Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key KAFKA-8531
...
We propose the change the default value of StreamsConfig.REPLICATION_FACTOR_CONFIG
from 1
to -1
(meaning use broker default). We also change the "importance level" of replication.factor
from HIGH
to MEDIUM
.
Compatibility, Deprecation, and Migration Plan
...
Note: if an existing application is upgrade, users won't be affected, because if internal replication/changleog topics exist already, no create topic request would be sent anyway. Only if a new application is deployed, or if an existing application is reset, and thus repartition/changelog topics would need to be created users might be affected. Because the application won't startup for this case, the impact is minor and can be considered non-critical. Applications already running in production won't break.
We also believe that 2.3.0 broker a sufficiently old such that not too many user may be affected, and we It is unclear how many users might be affected because they use older brokers than 2.4.0. However, we consider it an important improvement for default configs and want to take to opportunity of a major release to make this change (as it's technically breaking backward compatibility).
...