Why this matters
- VaultCommerce lost a broker during a zone outage — ISR-aware producers continued without data loss.
- Under-replicated partitions are the leading indicator of imminent unavailability.
- Leaders redistribute automatically via KRaft-controlled elections after broker failure.
- Understanding ISR explains why
acks=allalone is insufficient withoutmin.insync.replicas.
Producer
Leader P0Broker 1
Follower P0Broker 2
Follower P0Broker 3
Leader, followers, and fetch
Producers and consumers talk only to the leader for a partition. Followers replicate by fetching from the leader. When a follower catches up within replica.lag.time.max.ms, it joins the ISR. VaultCommerce alerts when ISR shrinks below 2 for any production topic.
Key points
- ISR (in-sync replicas) — followers within lag threshold; only ISR members count for
acks=all - Leader election — KRaft controller promotes a new leader from ISR on failure
- Under-replicated partition — leader has fewer ISR replicas than replication factor
- min.insync.replicas — minimum ISR size required to accept writes
- Preferred leader —
kafka-leader-electionrebalances leaders across brokers for even load
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 2 sections
- Unclean leader election
- VaultCommerce rollout checklist
Test yourself
Answer these before moving on — recall is what makes it stick.