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.
In more detail
The default is 1. With replication factor three and min.insync.replicas two, the topic keeps accepting writes after one broker fails but refuses them after two, rather than risk losing data. It has no effect on producers using acks 0 or 1.
Example
rpk topic alter-config orders --set min.insync.replicas=2Related terms
- in-sync replica set — The replicas of a partition that are currently caught up with the leader, abbreviated ISR.
- acks — The producer setting that decides how many brokers must confirm a record before the send counts as successful: 0, 1 or all.
- replication factor — The number of copies Kafka keeps of each partition, including the leader.
- NotEnoughReplicasError — The error a broker returns when an acks=all write cannot be accepted because fewer in-sync replicas exist than min.insync.replicas requires.
Taught in
- Acknowledged Is Not Always Safe — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Green Tests, Red Production — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Two Brokers Down — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Certificate That Expired On A Sunday — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Forty One Under-Replicated Partitions — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Data Centre That Went Dark — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Two Controllers At Once — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Night Before The Administrator Exam — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Acknowledgements: What Acks Means For Durability — Apache Kafka & Event Streaming
- In-Sync Replicas And Minimum ISR — Apache Kafka & Event Streaming
- Losing A Broker — Apache Kafka & Event Streaming