replication factor
The number of copies Kafka keeps of each partition, including the leader.
In more detail
A replication factor of three tolerates the loss of two brokers without losing committed data, provided the survivors were in sync. Production clusters typically use three, which is why they need at least three brokers.
Example
rpk topic create orders -p 3 -r 3Related terms
- replication — Keeping copies of data in more than one place, updated automatically, so one failure does not lose or block it.
- partition replica — One copy of a partition stored on one broker.
- min.insync.replicas — The topic or broker setting for the smallest number of in-sync replicas that must confirm an acks=all write for it to succeed.
- rpk topic create — An rpk command that creates one or more topics, optionally setting the partition count, replication factor and topic properties.
Taught in
- Where A Record Lands — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Acknowledged Is Not Always Safe — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Setting That Came Back — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Two Brokers Down — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Full Disks On Black Friday — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Night Before The Administrator Exam — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Three Brokers: Replication And Leaders — Apache Kafka & Event Streaming
- In-Sync Replicas And Minimum ISR — Apache Kafka & Event Streaming
- Losing A Broker — Apache Kafka & Event Streaming