Why tuning handles production load in Kafka - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the correct number of partitions for a Kafka topic.

Kafka

kafka-topics --create --topic my-topic --partitions [1] --replication-factor 3 --bootstrap-server localhost:9092

Drag options to blanks, or click blank then click option'

A10

B1

C0

D-1

Attempts:

3 left

💡 Hint

Common Mistakes

Setting partitions to 0 or negative values causes errors.

Using only 1 partition limits parallelism.

Setting partitions to 10 allows Kafka to handle more load by distributing messages across multiple partitions.

2fill in blank

medium

Complete the code to increase the Kafka producer batch size for better throughput.

Kafka

producerConfig.put("batch.size", [1]);

Drag options to blanks, or click blank then click option'

A"abc"

B"16384"

C"0"

D"-100"

Attempts:

3 left

💡 Hint

Common Mistakes

Using negative or zero batch size disables batching.

Using non-numeric values causes errors.

Setting batch.size to 16384 bytes allows the producer to send larger batches, improving throughput under load.

3fill in blank

hard

Fix the error in the consumer configuration to properly set the fetch max bytes.

Kafka

consumerConfig.put("fetch.max.bytes", [1]);

Drag options to blanks, or click blank then click option'

A"0"

B"-1"

C"one_mb"

D"1048576"

Attempts:

3 left

💡 Hint

Common Mistakes

Using negative or zero disables fetching.

Using non-numeric strings causes errors.

Setting fetch.max.bytes to 1048576 (1 MB) allows the consumer to fetch larger batches, improving performance under load.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps topic names to their partition counts if partitions are greater than 3.

Kafka

partitions_map = {topic: [1] for topic, partitions in topics.items() if partitions [2] 3}

Drag options to blanks, or click blank then click option'

Apartitions

Btopic

C>

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using topic as value instead of partitions.

Using '<' instead of '>' in condition.

This comprehension creates a dictionary with topics having more than 3 partitions, mapping topic names to their partition counts.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps uppercase topic names to their partition counts if partitions are less than or equal to 5.

Kafka

filtered = {{ [1]: [2] for [3], partitions in topics.items() if partitions <= 5 }}

Drag options to blanks, or click blank then click option'

Atopic.upper()

Bpartitions

Ctopic

Dpartitions.upper()

Attempts:

3 left

💡 Hint

Common Mistakes

Using partitions.upper() which is invalid.

Swapping key and value positions.

This comprehension maps uppercase topic names to their partition counts for topics with 5 or fewer partitions.

Practice

1. Why is tuning Kafka settings important for handling production load?

easy

A. It automatically fixes all network issues.

B. It changes the Kafka source code to add new features.

C. It reduces the number of Kafka brokers needed.

D. It helps Kafka process messages more efficiently under heavy load.

Solution

1. Step 1: Understand Kafka's role in message processing

   Kafka handles streams of messages, so efficient processing is key to avoid delays or failures.

2. Step 2: Recognize tuning impact on performance

   Tuning settings like batch size and timeouts helps Kafka manage more messages smoothly during high load.

3. Final Answer:

   It helps Kafka process messages more efficiently under heavy load. -> Option D

4. Quick Check:

   Tuning improves message handling = D [OK]

Hint: Tuning improves performance under load, not code or hardware [OK]

Common Mistakes:

• Thinking tuning changes Kafka code
• Assuming tuning reduces brokers automatically
• Believing tuning fixes network problems alone

2. Which Kafka configuration setting directly affects how many messages are sent in one batch?

easy

A. batch.size

B. max.poll.records

C. auto.offset.reset

D. log.retention.hours

Solution

1. Step 1: Identify batch-related settings

   Among the options, batch.size controls the number of bytes sent in one batch.

2. Step 2: Confirm other options' roles

   max.poll.records limits records fetched per poll, auto.offset.reset controls offset behavior, and log.retention.hours sets log retention time.

3. Final Answer:

   batch.size -> Option A

4. Quick Check:

   Batch size controls message batch = B [OK]

Hint: Batch size controls message grouping, not offsets or retention [OK]

Common Mistakes:

• Confusing batch.size with max.poll.records
• Mixing offset reset with batch size
• Thinking retention affects batch size

3. Given this Kafka producer config snippet:

{"batch.size": 16384, "linger.ms": 5}

What is the effect of setting linger.ms to 5?

medium

A. Kafka delays sending messages by 5 seconds.

B. Kafka waits up to 5 ms to batch more messages before sending.

C. Kafka sends messages immediately without waiting.

D. Kafka ignores batch size and sends single messages.

Solution

1. Step 1: Understand linger.ms meaning

   linger.ms sets how long Kafka waits to batch messages before sending.

2. Step 2: Interpret the value 5

   Setting it to 5 means Kafka waits up to 5 milliseconds to collect more messages for batching.

3. Final Answer:

   Kafka waits up to 5 ms to batch more messages before sending. -> Option B

4. Quick Check:

   linger.ms controls wait time = C [OK]

Hint: linger.ms sets wait time in milliseconds before sending batch [OK]

Common Mistakes:

• Thinking linger.ms is seconds, not milliseconds
• Assuming immediate send ignores linger.ms
• Confusing linger.ms with batch.size

4. You set num.network.threads to 1 on a Kafka broker but notice slow message processing under load. What is the likely issue?

medium

A. The batch size is too large.

B. Too many network threads cause CPU overload.

C. Too few network threads limit concurrent connections.

D. The retention period is too short.

Solution

1. Step 1: Understand num.network.threads role

   This setting controls how many threads handle network requests concurrently.

2. Step 2: Analyze effect of setting it to 1

   With only 1 thread, Kafka cannot handle many connections well, causing slow processing under load.

3. Final Answer:

   Too few network threads limit concurrent connections. -> Option C

4. Quick Check:

   Low network threads cause slow processing = A [OK]

Hint: Low network threads limit concurrency, causing slow processing [OK]

Common Mistakes:

• Blaming batch size or retention instead of threads
• Assuming more threads always cause overload
• Ignoring network thread impact on load

5. You want to improve Kafka producer throughput for a high-volume system. Which combination of tuning changes is best?

hard

A. Increase batch.size, increase linger.ms, and increase num.io.threads

B. Decrease batch.size, decrease linger.ms, and decrease num.io.threads

C. Increase batch.size, decrease linger.ms, and decrease num.io.threads

D. Decrease batch.size, increase linger.ms, and increase num.io.threads

Solution

1. Step 1: Understand batch.size and linger.ms effects

   Larger batch.size and higher linger.ms allow Kafka to batch more messages, improving throughput.

2. Step 2: Consider num.io.threads impact

   Increasing num.io.threads allows more parallel I/O operations, helping handle higher load.

3. Step 3: Evaluate options

   Increase batch.size, increase linger.ms, and increase num.io.threads increases all three to improve throughput; others reduce some settings, which lowers throughput.

4. Final Answer:

   Increase batch.size, increase linger.ms, and increase num.io.threads -> Option A

5. Quick Check:

   Increase batch, linger, and I/O threads = A [OK]

Hint: Increase batch size, linger time, and I/O threads for throughput [OK]

Common Mistakes:

• Reducing batch size or linger.ms when throughput is needed
• Decreasing I/O threads limits parallelism
• Mixing increase and decrease incorrectly