Disk I/O optimization in Kafka - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the log segment size to 1 GB for better disk I/O performance.

Kafka

props.put("log.segment.bytes", [1]);

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

A2048

B1048576

C512000

D1073741824

Attempts:

3 left

💡 Hint

Common Mistakes

Using 1048576 which is 1 MB instead of 1 GB.

Using too small values causing frequent segment rollovers.

The log segment size is set in bytes. 1 GB equals 1073741824 bytes, which helps optimize disk I/O by reducing segment rollover frequency.

2fill in blank

medium

Complete the code to enable log preallocation to improve disk write performance.

Kafka

props.put("log.preallocate", [1]);

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

A"false"

B"true"

C"auto"

D"enabled"

Attempts:

3 left

💡 Hint

Common Mistakes

Using "false" disables preallocation, reducing performance benefits.

Using invalid strings like "auto" or "enabled" which are not accepted.

Setting log.preallocate to "true" enables preallocation of log files, which can reduce disk fragmentation and improve write performance.

3fill in blank

hard

Fix the error in the code to correctly configure the flush interval to 5000 milliseconds.

Kafka

props.put("log.flush.interval.ms", [1]);

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

A5000

B5

C"5000"

D"five thousand"

Attempts:

3 left

💡 Hint

Common Mistakes

Using an integer without quotes causes a type error.

Using words instead of numeric strings.

The value for log.flush.interval.ms must be a string representing the number of milliseconds. So it should be "5000" with quotes.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that sets log retention to 7 days and segment bytes to 1 GB.

Kafka

config = {"log.retention.hours": [1], "log.segment.bytes": [2]

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

A"168"

B"604800000"

C1073741824

D168

Attempts:

3 left

💡 Hint

Common Mistakes

Using retention as integer instead of string.

Using incorrect byte size for segment bytes.

Retention is set in hours as a string "168" (7 days * 24 hours). Segment bytes is set as integer 1073741824 (1 GB).

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that sets flush interval to 1000 ms, enables preallocation, and sets segment bytes to 512 MB.

Kafka

config = {"log.flush.interval.ms": [1], "log.preallocate": [2], "log.segment.bytes": [3]

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

A"1000"

B"true"

C536870912

D1000

Attempts:

3 left

💡 Hint

Common Mistakes

Using integer 1000 instead of string "1000" for flush interval.

Using "false" instead of "true" for preallocation.

Incorrect byte size for 512 MB.

The flush interval must be a string "1000" ms, preallocation enabled with string "true", and segment bytes set to 512 MB (536870912 bytes).

Practice

1. Which Kafka configuration setting primarily affects how many threads handle disk read and write operations?

easy

A. num.io.threads

B. log.retention.hours

C. zookeeper.connect

D. auto.create.topics.enable

Solution

1. Step 1: Identify the setting related to disk I/O threads

   The setting num.io.threads controls the number of threads Kafka uses for disk input/output operations.

2. Step 2: Compare other options for relevance

   Other options like log.retention.hours relate to data retention, zookeeper.connect is for cluster coordination, and auto.create.topics.enable controls topic creation, none affect disk I/O threads.

3. Final Answer:

   num.io.threads -> Option A

4. Quick Check:

   Disk I/O threads = num.io.threads [OK]

Hint: Look for settings with 'io.threads' for disk I/O control [OK]

Common Mistakes:

• Confusing retention settings with I/O threads
• Choosing zookeeper settings instead of I/O
• Selecting topic creation options

2. Which of the following is the correct syntax to set the log segment size to 1 GB in Kafka's server.properties file?

easy

A. log.segment.bytes=1GB

B. log.segment.size=1GB

C. segment.log.bytes=1024

D. log.segment.bytes=1073741824

Solution

1. Step 1: Understand Kafka's configuration syntax for sizes

   Kafka expects byte values as integers for size settings, so 1 GB must be expressed in bytes (1 GB = 1073741824 bytes).

2. Step 2: Evaluate each option's correctness

   log.segment.bytes=1073741824 uses the correct key log.segment.bytes and the correct byte value. log.segment.size=1GB uses an invalid key and unit. segment.log.bytes=1024 uses wrong key and too small value. log.segment.bytes=1GB uses correct key but invalid unit '1GB'.

3. Final Answer:

   log.segment.bytes=1073741824 -> Option D

4. Quick Check:

   Size in bytes = 1073741824 [OK]

Hint: Use bytes as integer for size settings, no units like GB [OK]

Common Mistakes:

• Using units like GB instead of bytes
• Incorrect property names
• Using too small or wrong numeric values

3. Given the following Kafka configuration snippet:

num.io.threads=4
log.segment.bytes=10485760
log.dirs=/kafka-logs

What is the effect of setting num.io.threads to 4?

medium

A. Kafka limits the number of topics to 4.

B. Kafka will create 4 log directories.

C. Kafka will use 4 threads to handle disk I/O operations, improving parallelism.

D. Kafka will retain logs for 4 hours.

Solution

1. Step 1: Understand the role of num.io.threads

   This setting controls how many threads Kafka uses for disk input/output operations, allowing parallel reads and writes.

2. Step 2: Check other options for relevance

   Options about limiting topics, creating directories, or retention hours do not relate to num.io.threads.

3. Final Answer:

   Kafka will use 4 threads to handle disk I/O operations, improving parallelism. -> Option C

4. Quick Check:

   num.io.threads = 4 threads for disk I/O [OK]

Hint: num.io.threads sets disk I/O thread count, not topics or retention [OK]

Common Mistakes:

• Confusing thread count with topic count
• Assuming it controls log retention
• Thinking it creates multiple directories

4. You have set log.segment.bytes=10485760 but Kafka still creates very small log segments. What is the most likely cause?

medium

A. The log.roll.ms setting causes segments to roll before reaching the size limit.

B. The num.io.threads is too low.

C. The log.dirs path is incorrect.

D. Kafka does not support segment size configuration.

Solution

1. Step 1: Understand segment rolling behavior

   Kafka rolls log segments based on size or time. If log.roll.ms is set low, segments roll by time before reaching the size limit.

2. Step 2: Evaluate other options

   Low num.io.threads affects performance but not segment size. Incorrect log.dirs causes errors but not small segments. Kafka supports segment size configuration.

3. Final Answer:

   The log.roll.ms setting causes segments to roll before reaching the size limit. -> Option A

4. Quick Check:

   Segment rolling time overrides size limit [OK]

Hint: Check log.roll.ms if segments are smaller than expected [OK]

Common Mistakes:

• Blaming I/O threads for segment size
• Ignoring time-based rolling settings
• Assuming Kafka ignores segment size config

5. You want to optimize Kafka disk I/O for a high-throughput system. Which combination of settings is best to improve write performance without increasing disk usage too much?

hard

A. Decrease num.io.threads, set very large log.segment.bytes, and disable flushing

B. Increase num.io.threads, set moderate log.segment.bytes, and tune log.flush.interval.messages

C. Set num.io.threads to 1, use small log.segment.bytes, and flush after every message

D. Ignore num.io.threads, set log.segment.bytes to default, and increase retention time

Solution

1. Step 1: Understand the impact of num.io.threads and segment size

   Increasing num.io.threads allows more parallel disk operations. Moderate segment size balances write efficiency and disk usage.

2. Step 2: Consider flushing settings

   Tuning log.flush.interval.messages controls how often data is flushed to disk, improving performance without excessive disk writes.

3. Step 3: Evaluate other options

   Decreasing threads or disabling flushing harms performance or data safety. Small segments and frequent flushes increase disk I/O. Ignoring threads or retention does not optimize writes.

4. Final Answer:

   Increase num.io.threads, set moderate log.segment.bytes, and tune log.flush.interval.messages -> Option B

5. Quick Check:

   Balanced threads, segment size, and flush tuning optimize disk I/O [OK]

Hint: Balance threads, segment size, and flush interval for best write speed [OK]

Common Mistakes:

• Setting too large segments causing disk bloat
• Disabling flushing risking data loss
• Using too few I/O threads limiting throughput