Leader election in Kafka - Mini Project: Build & Apply

Leader election

📖 Scenario: You are working with a Kafka cluster where multiple brokers participate in leader election for partitions. Understanding how leader election works helps ensure high availability and fault tolerance in distributed systems.

🎯 Goal: Build a simple Kafka leader election simulation using Python to understand how a leader is chosen from a list of brokers.

📋 What You'll Learn

Create a list of broker IDs

Set a threshold to decide leader eligibility

Use a comprehension to select eligible leaders

Print the chosen leader

💡 Why This Matters

🌍 Real World

Leader election is a key part of distributed systems like Kafka to decide which broker manages a partition.

💼 Career

Understanding leader election helps in roles like DevOps, Site Reliability Engineering, and backend development where managing distributed systems is common.

1

Create the list of brokers

Create a list called brokers with these exact integer values: 101, 102, 103, 104, 105.

Kafka

# Create a list called brokers with the given broker IDs
# Your code here

Hint

Use square brackets to create a list and separate values with commas.

2

Set the leader eligibility threshold

Create a variable called leader_threshold and set it to 103.

Kafka

brokers = [101, 102, 103, 104, 105]
# Create a variable leader_threshold and set it to 103
# Your code here

Hint

Assign the number 103 to the variable leader_threshold.

3

Select eligible leaders using list comprehension

Create a list called eligible_leaders using a list comprehension that includes only brokers from brokers with IDs greater than or equal to leader_threshold.

Kafka

brokers = [101, 102, 103, 104, 105]
leader_threshold = 103
# Create eligible_leaders list with brokers >= leader_threshold using list comprehension
# Your code here

Hint

Use a list comprehension with an if condition to filter brokers.

4

Print the chosen leader

Print the smallest broker ID from eligible_leaders as the chosen leader using print().

Kafka

brokers = [101, 102, 103, 104, 105]
leader_threshold = 103
eligible_leaders = [broker for broker in brokers if broker >= leader_threshold]
# Print the smallest broker ID from eligible_leaders
# Your code here

Hint

Use the min() function to find the smallest ID in the list.

Practice

1. What is the main purpose of leader election in Kafka?

easy

A. To backup data to external storage

B. To balance the load evenly among all brokers

C. To choose one broker to lead and coordinate tasks

D. To monitor client connections

Solution

1. Step 1: Understand leader election role

   Leader election picks one broker as the leader to manage partition tasks.

2. Step 2: Compare options

   Only To choose one broker to lead and coordinate tasks describes choosing a broker to lead and coordinate tasks, which matches Kafka's leader election purpose.

3. Final Answer:

   To choose one broker to lead and coordinate tasks -> Option C

4. Quick Check:

   Leader election = choose leader broker [OK]

Hint: Leader election picks one leader broker, not all brokers [OK]

Common Mistakes:

• Confusing leader election with load balancing
• Thinking leader election backs up data
• Assuming leader election monitors clients

2. Which of the following is the correct way to configure Kafka broker IDs for leader election?

easy

A. broker.id=unique_integer_per_broker

B. broker.id=localhost

C. broker.id=auto_assign

D. broker.id=0.0.0.0

Solution

1. Step 1: Identify broker ID type

   Kafka requires each broker to have a unique integer ID for leader election.

2. Step 2: Check options

   Only broker.id=unique_integer_per_broker uses a unique integer, while others use invalid or non-integer values.

3. Final Answer:

   broker.id=unique_integer_per_broker -> Option A

4. Quick Check:

   Broker ID must be unique integer [OK]

Hint: Broker ID must be a unique integer, not a string or IP [OK]

Common Mistakes:

• Using hostnames or IPs as broker IDs
• Setting broker.id to zero or non-unique values
• Assuming auto assignment works without config

3. Given the following Kafka cluster state, which broker will be the leader for partition 0?

Broker 1: ISR = [1, 2, 3]
Broker 2: ISR = [1, 2, 3]
Broker 3: ISR = [1, 2, 3]
Current leader: Broker 2
Broker 2 fails

medium

A. Broker 2

B. Broker 1

C. Broker 3

D. No leader assigned

Solution

1. Step 1: Understand ISR and leader failover

   ISR (In-Sync Replicas) are eligible leaders. When current leader fails, next ISR broker becomes leader.

2. Step 2: Identify next leader after Broker 2 fails

   Broker 1 and 3 are in ISR. Kafka picks the lowest broker ID in ISR as new leader, so Broker 1.

3. Final Answer:

   Broker 1 -> Option B

4. Quick Check:

   Next leader = lowest ISR broker after failure [OK]

Hint: Leader election picks lowest ISR broker if current leader fails [OK]

Common Mistakes:

• Choosing failed broker as leader
• Picking broker outside ISR
• Assuming no leader assigned after failure

4. You have a Kafka cluster where leader election is not working properly. Which of the following is the most likely cause?

medium

A. Each broker has a unique broker.id

B. Zookeeper is running and connected

C. Partitions have multiple replicas

D. All brokers have the same broker.id

Solution

1. Step 1: Identify leader election requirements

   Leader election requires each broker to have a unique broker.id to distinguish them.

2. Step 2: Analyze causes

   If all brokers share the same broker.id, leader election cannot assign a unique leader, causing failure.

3. Final Answer:

   All brokers have the same broker.id -> Option D

4. Quick Check:

   Unique broker IDs needed for leader election [OK]

Hint: Check broker IDs; duplicates break leader election [OK]

Common Mistakes:

• Assuming Zookeeper connection causes failure
• Thinking multiple replicas cause election failure
• Ignoring broker.id uniqueness

5. In a Kafka cluster using KRaft mode (without Zookeeper), how does leader election differ from the traditional Zookeeper-based approach?

hard

A. KRaft uses an internal quorum of controllers to elect leaders without external Zookeeper

B. KRaft requires manual leader assignment by the admin

C. KRaft disables leader election and uses round-robin partition assignment

D. KRaft uses Zookeeper but with a different election algorithm

Solution

1. Step 1: Understand KRaft mode leader election

   KRaft mode replaces Zookeeper with an internal controller quorum that manages leader election.

2. Step 2: Compare options

   Only KRaft uses an internal quorum of controllers to elect leaders without external Zookeeper correctly states KRaft uses internal quorum without external Zookeeper for leader election.

3. Final Answer:

   KRaft uses an internal quorum of controllers to elect leaders without external Zookeeper -> Option A

4. Quick Check:

   KRaft = internal quorum leader election [OK]

Hint: KRaft replaces Zookeeper with internal controller quorum [OK]

Common Mistakes:

• Thinking KRaft disables leader election
• Assuming manual leader assignment in KRaft
• Believing KRaft still uses external Zookeeper