บทบาทของตัวควบคุมและ ZooKeeper/Kraft

Imagine a bustling city. To keep everything running smoothly, you need a central command center, right?

A Kafka cluster, with its many brokers and distributed data, also needs a 'brain' to coordinate its activities. This is where the Kafka Controller comes in.

The Kafka Controller is a special role taken on by one of the Kafka brokers in the cluster. Only one broker can be the controller at any given time.

• It's elected from the available brokers.
• It acts as the primary coordinator for the entire cluster.
• If the current controller fails, another broker is elected to take its place.

The Controller has critical duties to ensure the Kafka cluster operates correctly. Think of it as the cluster's manager.

• Partition Leader Election: Decides which broker becomes the leader for a topic partition.
• Broker Failure Handling: Detects when a broker goes offline and reassigns its leaders.
• Topic Management: Oversees the creation, deletion, and modification of topics and their partitions.
• Cluster Metadata: Keeps track of the cluster's state, like active brokers and partition assignments.

To ensure there's always one, and only one, active Controller, Kafka relies on a consensus mechanism. This mechanism helps brokers agree on who the current Controller is.

Historically, Kafka used an external system called ZooKeeper for this. More recently, Kafka introduced Kraft (Kafka Raft Metadata mode) to handle this internally.

For many years, Apache ZooKeeper was an essential part of a Kafka deployment. It's a separate, distributed coordination service.

ZooKeeper provided a highly reliable way for Kafka brokers to share critical information and elect a Controller.

In a Kafka cluster using ZooKeeper, ZooKeeper was responsible for:

• Controller Election: Facilitating the election of the active Kafka Controller.
• Cluster Metadata Storage: Storing metadata like broker IDs, topic configurations, and partition assignments.
• Broker Registration: Brokers would register themselves with ZooKeeper when they started up.
• Failure Detection: Notifying the Controller if a broker or another component failed.

While effective, using ZooKeeper came with its own set of challenges:

• Operational Complexity: You had to deploy and manage two separate distributed systems (Kafka and ZooKeeper).
• Version Compatibility: Keeping Kafka and ZooKeeper versions compatible could be tricky.
• Performance: Metadata operations had to go through ZooKeeper, which could sometimes be a bottleneck.

To simplify Kafka's architecture and improve performance, the community introduced Kraft (Kafka Raft Metadata mode). Kraft replaces ZooKeeper for metadata management and Controller election.

It's an implementation of the Raft consensus algorithm directly within Kafka.

With Kraft, Kafka becomes a single, self-managed distributed system. This brings significant advantages:

• Simplified Architecture: No separate ZooKeeper cluster to manage.
• Faster Startup: Brokers can start up quicker without waiting for ZooKeeper.
• Improved Metadata Performance: Direct Raft communication is faster than going through ZooKeeper.
• Unified Deployment: Easier to deploy and operate Kafka clusters.

In this lesson, we explored the crucial roles of the Kafka Controller and the underlying consensus mechanisms.

• The Controller is a single broker managing cluster state and partition leadership.
• ZooKeeper was the traditional external service for Controller election and metadata storage.
• Kraft is the modern, built-in Raft-based protocol that simplifies Kafka by removing the ZooKeeper dependency, handling Controller election and metadata internally.

Understanding these components is key to grasping how Kafka maintains its robust and distributed nature!