zombie fencing
Blocking an old instance of a transactional producer from writing once a newer instance with the same transactional ID has started.
In more detail
A zombie is a producer that was thought dead, for example after a long pause, but comes back and keeps sending. The broker rejects its writes because its epoch is older, which prevents duplicate or conflicting transactions.
Related terms
- transactional.id — A stable name you give a transactional producer so the broker can recognise it across restarts.
- Kafka transaction — A group of writes, possibly across several partitions and topics, that Kafka makes visible all together on commit or not at all on abort.
Taught in
- The Error Storm That Fixes Itself — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Two Copies Of One Service — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Forty One Under-Replicated Partitions — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Night Before The Administrator Exam — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Transactions And Exactly Once Semantics — Apache Kafka & Event Streaming