This ensures that when using automatic Kafka topic creation, with more than one
node in the Kafka cluster, all partitions in the topic are automatically
replicated. When a single node goes down in a >=3 node cluster, these topics will
continue to accept writes providing there are at least two insync replicas.
In a two node cluster, no failures are tolerated. In a three node cluster, only a
single node failure is tolerated. In a larger cluster the configuration may need
manual tuning.
Reviewed: https:/ /review. opendev. org/743296 /git.openstack. org/cgit/ openstack/ kolla-ansible/ commit/ ?id=a82e233706e 2da87c9ef613eaa 04559b66089230
Committed: https:/
Submitter: Zuul
Branch: stable/ussuri
commit a82e233706e2da8 7c9ef613eaa0455 9b66089230
Author: Doug Szumski <email address hidden>
Date: Wed Jul 22 17:18:26 2020 +0100
Set Kafka default replication factor
This ensures that when using automatic Kafka topic creation, with more than one
node in the Kafka cluster, all partitions in the topic are automatically
replicated. When a single node goes down in a >=3 node cluster, these topics will
continue to accept writes providing there are at least two insync replicas.
In a two node cluster, no failures are tolerated. In a three node cluster, only a
single node failure is tolerated. In a larger cluster the configuration may need
manual tuning.
This configuration follows advice given here:
[1] https:/ /docs.cloudera. com/documentati on/kafka/ 1-2-x/topics/ kafka_ha. html#xd_ 583c10bfdbd326b a-590cb1d1- 149e9ca9886- -6fec__ section_ d2t_ff2_ lq
Closes-Bug: #1888522
Change-Id: I7d38c6ccb22061 aa88d9ac6e2e25c 3e095fdb8c3 c3d607bff220309 ca3b3b0bd7)
(cherry picked from commit a273e28e208eaf7