Memory and buffer configuration in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the role of the buffer.memory setting in Kafka producer configuration?

It sets the total bytes of memory the producer can use to buffer records waiting to be sent to the server. If records are sent faster than they can be delivered, this buffer helps manage the load.

beginner

Explain the batch.size configuration in Kafka producer.

It defines the maximum size (in bytes) of a batch of records sent to a partition. Larger batches improve throughput but may increase latency.

beginner

What does linger.ms control in Kafka producer settings?

It controls how long the producer waits before sending a batch of records. Waiting allows more records to accumulate in a batch, improving efficiency.

intermediate

How does fetch.min.bytes affect Kafka consumer memory usage?

It sets the minimum amount of data the consumer wants to fetch from the broker. Larger values can reduce the number of fetch requests but increase memory usage.

intermediate

What is the purpose of max.partition.fetch.bytes in Kafka consumer configuration?

It limits the maximum bytes fetched per partition in a single fetch request. This controls memory usage and prevents fetching too much data at once.

What does the buffer.memory setting in Kafka producer control?

A Maximum size of a single record

B Total memory for buffering records before sending

C Time to wait before sending a batch

D Maximum fetch size for consumer

The buffer.memory controls the total bytes of memory the producer uses to buffer records before sending.

Which setting controls how long a Kafka producer waits to accumulate records before sending?

A linger.ms

B batch.size

C fetch.min.bytes

D max.partition.fetch.bytes

linger.ms sets the wait time before sending a batch to allow more records to accumulate.

Increasing batch.size in Kafka producer will likely:

A Decrease throughput

B Have no effect

C Increase throughput and may increase latency

D Decrease memory usage

Larger batch.size can increase throughput but may increase latency due to waiting for batch to fill.

What does fetch.min.bytes affect in Kafka consumer?

A Minimum bytes to fetch per request

B Maximum bytes to fetch per partition

C Producer buffer size

D Batch size for producer

fetch.min.bytes sets the minimum amount of data the consumer wants to fetch in one request.

Why limit max.partition.fetch.bytes in Kafka consumer?

A To control linger time

B To reduce producer memory usage

C To increase batch size

D To limit memory used per partition fetch

max.partition.fetch.bytes limits the maximum bytes fetched per partition to control memory usage.

Describe how Kafka producer memory and buffer settings like buffer.memory, batch.size, and linger.ms work together to optimize performance.

Think about how buffering and batching help manage data flow.

Explain the impact of Kafka consumer settings fetch.min.bytes and max.partition.fetch.bytes on memory usage and data fetching.

Consider how much data the consumer requests and stores.

Practice

1. Which Kafka configuration setting controls the size of the buffer used to batch data before sending to brokers?

easy

A. fetch.min.bytes

B. batch.size

C. buffer.memory

D. linger.ms

Solution

1. Step 1: Understand buffer settings in Kafka producer

   The batch.size setting controls the maximum size of a batch of records sent to brokers.

2. Step 2: Differentiate from other buffer-related settings

   buffer.memory controls total memory for buffering, fetch.min.bytes is for consumers, and linger.ms controls delay before sending batches.

3. Final Answer:

   batch.size -> Option B

4. Quick Check:

   Batch size controls batch buffer size [OK]

Hint: Batch size sets buffer for sending data batches [OK]

Common Mistakes:

• Confusing total buffer memory with batch size
• Mixing consumer fetch settings with producer buffers
• Thinking linger.ms controls buffer size

2. Which of the following is the correct syntax to set the buffer memory size to 32MB in Kafka producer properties file?

easy

A. buffer.memory=33554432

B. buffer.memory=32

C. buffer.memory=32m

D. buffer.memory=32MB

Solution

1. Step 1: Understand Kafka config value units

   Kafka expects buffer.memory in bytes, not with units like MB or m.

2. Step 2: Convert 32MB to bytes

   32MB = 32 * 1024 * 1024 = 33554432 bytes, so the value must be numeric bytes.

3. Final Answer:

   buffer.memory=33554432 -> Option A

4. Quick Check:

   Buffer memory uses bytes, not MB string [OK]

Hint: Use bytes number, not MB string, for buffer.memory [OK]

Common Mistakes:

• Adding MB or m suffix which Kafka does not parse
• Using too small number without units
• Confusing buffer.memory with batch.size units

3. Given this Kafka producer config snippet:

buffer.memory=1048576
batch.size=16384
linger.ms=10

What is the maximum amount of data (in bytes) that can be buffered before sending?

medium

A. 1048586 bytes

B. 16384 bytes

C. 1048576 bytes

D. 10 bytes

Solution

1. Step 1: Identify buffer.memory meaning

   buffer.memory is the total bytes available to buffer records waiting to be sent.

2. Step 2: Understand batch.size role

   batch.size is max size per batch, but total buffer can hold multiple batches up to buffer.memory.

3. Final Answer:

   1048576 bytes -> Option C

4. Quick Check:

   Total buffer memory = 1048576 bytes [OK]

Hint: buffer.memory is total buffer size, batch.size is per batch [OK]

Common Mistakes:

• Confusing batch.size as total buffer
• Adding linger.ms value to buffer size
• Choosing sum of batch.size and buffer.memory

4. You set buffer.memory=1024 and batch.size=2048 in Kafka producer config. What issue will occur?

medium

A. Producer will throw a configuration error on startup

B. No issue; Kafka adjusts batch.size automatically

C. Producer will silently drop messages exceeding buffer.memory

D. Producer will block or throw an error when batch.size exceeds buffer.memory

Solution

1. Step 1: Compare batch.size and buffer.memory values

   Here, batch.size (2048) is larger than buffer.memory (1024), which is invalid.

2. Step 2: Kafka behavior on invalid buffer sizes

   Kafka producer will block or throw an error because it cannot allocate a batch larger than total buffer memory.

3. Final Answer:

   Producer will block or throw an error when batch.size exceeds buffer.memory -> Option D

4. Quick Check:

   batch.size must be ≤ buffer.memory [OK]

Hint: batch.size cannot be bigger than buffer.memory [OK]

Common Mistakes:

• Assuming Kafka auto-corrects batch.size
• Expecting silent message drops
• Thinking config error happens at startup

5. You want to optimize Kafka producer for low latency and high throughput. Which combination of memory and buffer settings is best?

hard

A. Increase buffer.memory, decrease linger.ms, increase batch.size

B. Decrease buffer.memory, increase linger.ms, decrease batch.size

C. Keep buffer.memory small, set linger.ms high, increase batch.size

D. Set buffer.memory and batch.size low, linger.ms high

Solution

1. Step 1: Understand latency vs throughput tradeoff

   Low latency means sending data quickly, high throughput means sending large batches efficiently.

2. Step 2: Adjust buffer and batch settings accordingly

   Increasing buffer.memory and batch.size allows bigger batches, while decreasing linger.ms reduces wait time before sending.

3. Final Answer:

   Increase buffer.memory, decrease linger.ms, increase batch.size -> Option A

4. Quick Check:

   Big buffer + big batch + low linger = low latency & high throughput [OK]

Hint: Big buffer and batch, low linger for speed and volume [OK]

Common Mistakes:

• Increasing linger.ms reduces latency
• Decreasing buffer.memory improves throughput
• Setting batch.size too low for throughput