Broker nodes in Kafka - Mini Project: Build & Apply

Broker Nodes in Kafka

📖 Scenario: You are setting up a Kafka cluster to handle messages for a small online store. Each Kafka broker node stores and manages messages. You want to create a simple list of broker nodes with their IDs and hostnames.

🎯 Goal: Create a dictionary representing Kafka broker nodes with their IDs as keys and hostnames as values. Then filter the brokers to find those with IDs greater than a certain threshold.

📋 What You'll Learn

Create a dictionary called brokers with broker IDs as keys and hostnames as values

Create a variable called threshold with the value 2

Create a new dictionary called filtered_brokers that includes only brokers with IDs greater than threshold

Print the filtered_brokers dictionary

💡 Why This Matters

🌍 Real World

Kafka brokers are servers that store and manage message data. Managing broker nodes helps in scaling and maintaining message systems.

💼 Career

Understanding how to work with broker nodes and filter them is useful for roles in data engineering, backend development, and system administration involving Kafka.

1

Create the initial broker nodes dictionary

Create a dictionary called brokers with these exact entries: 1: 'broker1.example.com', 2: 'broker2.example.com', 3: 'broker3.example.com', 4: 'broker4.example.com'

Kafka

# Create the brokers dictionary with IDs and hostnames
# Your code here

Hint

Use curly braces {} to create a dictionary with integer keys and string values.

2

Set the threshold for filtering brokers

Create a variable called threshold and set it to 2

Kafka

brokers = {1: 'broker1.example.com', 2: 'broker2.example.com', 3: 'broker3.example.com', 4: 'broker4.example.com'}
# Create the threshold variable and set it to 2
# Your code here

Hint

Just assign the number 2 to the variable threshold.

3

Filter brokers with IDs greater than threshold

Create a new dictionary called filtered_brokers that includes only the brokers from brokers where the broker ID is greater than threshold. Use a dictionary comprehension with broker_id and hostname as variables.

Kafka

brokers = {1: 'broker1.example.com', 2: 'broker2.example.com', 3: 'broker3.example.com', 4: 'broker4.example.com'}
threshold = 2
# Create filtered_brokers dictionary with brokers having IDs > threshold
# Your code here

Hint

Use a dictionary comprehension with for broker_id, hostname in brokers.items() and an if condition.

4

Print the filtered brokers

Write a print statement to display the filtered_brokers dictionary

Kafka

brokers = {1: 'broker1.example.com', 2: 'broker2.example.com', 3: 'broker3.example.com', 4: 'broker4.example.com'}
threshold = 2
filtered_brokers = {broker_id: hostname for broker_id, hostname in brokers.items() if broker_id > threshold}
# Print the filtered_brokers dictionary
# Your code here

Hint

Use print(filtered_brokers) to show the result.

Practice

1.

What is the primary role of a broker node in Kafka?

easy

A. Store and manage Kafka messages

B. Produce messages to topics

C. Consume messages from topics

D. Monitor network traffic

Solution

1. Step 1: Understand broker node function

   A broker node is a Kafka server that stores and manages messages.

2. Step 2: Differentiate roles

   Producers send messages, consumers read them, but brokers store/manage them.

3. Final Answer:

   Store and manage Kafka messages -> Option A

4. Quick Check:

   Broker = Store/manage messages [OK]

Hint: Broker nodes store messages; producers and consumers do not [OK]

Common Mistakes:

• Confusing brokers with producers or consumers
• Thinking brokers monitor network traffic
• Assuming brokers only route messages

2.

Which of the following is the correct way to specify a broker's unique ID in the Kafka server.properties file?

easy

A. broker.id=1

B. brokerID=1

C. broker-id=1

D. brokerId=1

Solution

1. Step 1: Recall Kafka broker ID syntax

   The correct property name is broker.id with a dot separator.

2. Step 2: Check options for exact match

   Only broker.id=1 matches Kafka's expected syntax.

3. Final Answer:

   broker.id=1 -> Option A

4. Quick Check:

   Broker ID property uses dot notation [OK]

Hint: Broker ID uses dot notation: broker.id [OK]

Common Mistakes:

• Using camelCase or hyphens instead of dot
• Misspelling the property name
• Confusing broker.id with other properties

3.

Given the following snippet from a Kafka server.properties file:

broker.id=2
listeners=PLAINTEXT://localhost:9093
log.dirs=/tmp/kafka-logs-2

What will be the broker's ID and listening port when Kafka starts?

medium

A. Broker ID 1, listening on port 9092

B. Broker ID 2, listening on port 9093

C. Broker ID 2, listening on port 9092

D. Broker ID 1, listening on port 9093

Solution

1. Step 1: Identify broker ID from properties

   The property broker.id=2 sets the broker ID to 2.

2. Step 2: Identify listener port

   listeners=PLAINTEXT://localhost:9093 means the broker listens on port 9093.

3. Final Answer:

   Broker ID 2, listening on port 9093 -> Option B

4. Quick Check:

   broker.id=2 and port=9093 [OK]

Hint: Broker ID and port come directly from properties file [OK]

Common Mistakes:

• Assuming default port 9092 without checking listeners
• Mixing up broker IDs
• Ignoring the listeners property

4.

Consider this server.properties snippet:

broker.id=abc
listeners=PLAINTEXT://localhost:9092

What is the issue when starting Kafka with this configuration?

medium

A. broker.id can be a string, so no issue

B. listeners property is missing a port

C. Kafka will ignore broker.id and assign default

D. broker.id must be an integer, so 'abc' causes an error

Solution

1. Step 1: Check broker.id value type

   Kafka requires broker.id to be an integer number.

2. Step 2: Identify invalid value

   Setting broker.id=abc is invalid and causes startup error.

3. Final Answer:

   broker.id must be an integer, so 'abc' causes an error -> Option D

4. Quick Check:

   broker.id integer required [OK]

Hint: broker.id must be a number, not letters [OK]

Common Mistakes:

• Assuming broker.id can be string
• Ignoring error messages on startup
• Thinking Kafka assigns default broker.id automatically

5.

You want to run three Kafka broker nodes on the same machine for testing. Which configuration change is essential for each broker to avoid conflicts?

hard

A. Use the same broker.id but different log.dirs

B. Keep listeners port same but change broker.id

C. Assign unique broker.id and different listeners ports

D. Only change log.dirs for each broker

Solution

1. Step 1: Understand broker uniqueness requirements

   Each broker must have a unique broker.id to identify it in the cluster.

2. Step 2: Avoid port conflicts

   Each broker must listen on a different port to avoid network conflicts.

3. Final Answer:

   Assign unique broker.id and different listeners ports -> Option C

4. Quick Check:

   Unique IDs and ports prevent conflicts [OK]

Hint: Unique broker.id and ports prevent conflicts [OK]

Common Mistakes:

• Using same broker.id for multiple brokers
• Using same port for multiple brokers
• Only changing log directories without ports or IDs