Partition key and routing in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a partition key in Kafka?

A partition key is a value used to decide which partition a message will go to within a Kafka topic. It helps organize messages so related data stays together.

beginner

How does Kafka use the partition key for routing messages?

Kafka applies a hash function to the partition key. The result determines the partition number where the message is stored, ensuring messages with the same key go to the same partition.

intermediate

Why is it important to use a partition key in Kafka?

Using a partition key ensures message order for related data and balances load across partitions. Without it, messages might be distributed randomly, losing order and grouping.

intermediate

What happens if a message is sent without a partition key in Kafka?

If no partition key is provided, Kafka distributes messages in a round-robin way across partitions. This can improve load balancing but may lose message order for related data.

advanced

Explain the relationship between partition key and consumer groups in Kafka.

Partition keys determine message placement in partitions. Consumer groups read from partitions independently, so messages with the same key go to the same partition and are processed in order by one consumer.

What does Kafka use to decide the partition for a message?

A Message size

B Random number generator

C Timestamp of the message

D Hash of the partition key

Kafka uses a hash function on the partition key to determine the partition.

What happens if you send a Kafka message without a partition key?

A Message is dropped

B Message goes to a random partition

C Message is sent to all partitions

D Message is sent to partition 0 only

Without a partition key, Kafka distributes messages in a round-robin fashion across partitions.

Why use a partition key in Kafka?

A To ensure message order for related data

B To encrypt messages

C To compress messages

D To increase message size

Partition keys help keep related messages in the same partition, preserving order.

Which of these is true about Kafka partitions?

A Each partition can be read by multiple consumers in the same group simultaneously

B Messages in a partition are unordered

C Messages with the same partition key go to the same partition

D Partitions are created dynamically by consumers

Messages with the same partition key always go to the same partition.

How does Kafka ensure load balancing when no partition key is used?

A By round-robin distribution across partitions

B By sending all messages to one partition

C By hashing the message content

D By using the message timestamp

Kafka uses round-robin distribution to balance load when no partition key is provided.

Describe how Kafka uses a partition key to route messages to partitions.

Think about how hashing helps keep related messages together.

Explain the impact of not using a partition key when sending messages in Kafka.

Consider what happens to message order and partition choice.

Practice

1. What is the main purpose of using a partition key in Kafka?

easy

A. To increase the message size limit

B. To encrypt the message content

C. To ensure related messages go to the same partition

D. To compress the message before sending

Solution

1. Step 1: Understand partition key role

   The partition key is used to decide which partition a message goes to in Kafka.

2. Step 2: Connect key to message ordering

   Using the same key ensures related messages stay in the same partition, preserving order.

3. Final Answer:

   To ensure related messages go to the same partition -> Option C

4. Quick Check:

   Partition key controls message placement = D [OK]

Hint: Partition key groups related messages together [OK]

Common Mistakes:

• Thinking partition key encrypts messages
• Confusing partition key with compression
• Believing partition key increases message size

2. Which of the following is the correct way to specify a partition key when producing a Kafka message in Java?

easy

A. producer.send(new ProducerRecord<>(topic, value));

B. producer.send(new ProducerRecord<>(value, key));

C. producer.send(new ProducerRecord<>(key, topic, value));

D. producer.send(new ProducerRecord<>(topic, key, value));

Solution

1. Step 1: Recall ProducerRecord constructor

   The correct constructor order is (topic, key, value) to specify partition key.

2. Step 2: Match options to constructor

   producer.send(new ProducerRecord<>(topic, key, value)); matches this order exactly, others mix parameters incorrectly.

3. Final Answer:

   producer.send(new ProducerRecord<>(topic, key, value)); -> Option D

4. Quick Check:

   Topic, key, value order = B [OK]

Hint: Remember ProducerRecord(topic, key, value) order [OK]

Common Mistakes:

• Swapping key and value positions
• Omitting the key parameter
• Placing key before topic incorrectly

3. Given a Kafka topic with 3 partitions, what will happen if you send messages with the same partition key "user123" repeatedly?

medium

A. All messages will go to the same partition

B. Messages will be evenly distributed across all partitions

C. Messages will be sent to partition 0 only

D. Messages will be randomly assigned to any partition

Solution

1. Step 1: Understand partition key hashing

   Kafka hashes the partition key to decide the partition number.

2. Step 2: Same key means same hash and partition

   Repeated messages with "user123" key will always hash to the same partition.

3. Final Answer:

   All messages will go to the same partition -> Option A

4. Quick Check:

   Same key -> same partition = C [OK]

Hint: Same key always hashes to same partition [OK]

Common Mistakes:

• Assuming keys distribute evenly without hashing
• Thinking messages go to partition 0 by default
• Believing messages are randomly assigned despite keys

4. You wrote this code to send messages with keys but all messages end up in different partitions. What is the likely mistake?

producer.send(new ProducerRecord<>(topic, null, value));

medium

A. The topic name is missing

B. The key is null, so messages are distributed randomly

C. The value is null, causing errors

D. ProducerRecord constructor is used incorrectly

Solution

1. Step 1: Check the key parameter

   The key is set to null, so Kafka cannot use it for partitioning.

2. Step 2: Understand default partitioning behavior

   Without a key, Kafka distributes messages randomly across partitions.

3. Final Answer:

   The key is null, so messages are distributed randomly -> Option B

4. Quick Check:

   Null key -> random partitions = A [OK]

Hint: Null key means random partition assignment [OK]

Common Mistakes:

• Assuming null key sends to partition 0
• Confusing missing topic with null key
• Thinking null value causes partitioning issues

5. You want to ensure that messages related to the same customer ID always go to the same partition, but your customer IDs sometimes are null or empty strings. How should you handle partition keys to maintain message order for valid IDs and avoid errors?

hard

A. Use the customer ID as key only if it is non-empty; otherwise, assign a default fixed key

B. Always send messages with null keys to let Kafka distribute randomly

C. Convert null or empty IDs to random UUIDs as keys

D. Ignore keys and rely on Kafka's default partitioning

Solution

1. Step 1: Identify the problem with null or empty keys

   Null or empty keys cause Kafka to distribute messages randomly, breaking order.

2. Step 2: Use a default fixed key for missing IDs

   Assigning a fixed key for missing IDs groups those messages in one partition, preserving order for them.

3. Step 3: Keep valid customer IDs as keys

   Valid IDs remain keys to ensure their messages go to the same partition.

4. Final Answer:

   Use the customer ID as key only if it is non-empty; otherwise, assign a default fixed key -> Option A

5. Quick Check:

   Non-empty key or default fixed key = A [OK]

Hint: Use default key for missing IDs to keep order [OK]

Common Mistakes:

• Sending null keys causing random partitioning
• Using random UUIDs breaking message grouping
• Ignoring keys and losing message order