Kafka controller
The broker currently responsible for cluster-wide decisions such as tracking brokers and choosing partition leaders.
In more detail
Apache Kafka 4.x elects its controller through the KRaft consensus protocol, and Redpanda uses the Raft protocol for the same job. rpk cluster info marks the controller with an asterisk. If the controller fails, another broker takes over automatically.
Related terms
- Kafka cluster — A group of brokers that share the same topics and metadata and act as one Kafka service.
- leader election — The process by which the members of a distributed system choose one of themselves to act as leader.
- broker — A server that receives messages from producers, stores them and delivers them to consumers, such as RabbitMQ or Apache Kafka.
Taught in
- The Error Storm That Fixes Itself — 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
- The New Broker That Did Nothing — 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
- Forty Minutes To Start — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Upgrade That Could Not Start — 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
- Starting A Broker And Reading Its Metadata — Apache Kafka & Event Streaming