Retention policies (time-based, size-based) in Kafka - Time & Space Complexity

Time Complexity: Retention policies (time-based, size-based)

O(n)

Understanding Time Complexity

When Kafka manages data retention, it must decide which messages to keep or delete.

We want to understand how the work Kafka does grows as data or time limits change.

Scenario Under Consideration

Analyze the time complexity of Kafka's retention check process.

// Pseudocode for retention check
for each partition in topic:
  for each segment in partition:
    if segment is older than retention time or segment size exceeds limit:
      delete segment

This code checks each data segment in partitions to decide if it should be deleted based on time or size limits.

Identify Repeating Operations

Look at what repeats in this process.

• Primary operation: Looping over all segments in all partitions.
• How many times: Once per segment, for every partition in the topic.

How Execution Grows With Input

As the number of partitions and segments grows, the checks grow too.

Input Size (n)	Approx. Operations
10 segments	10 checks
100 segments	100 checks
1000 segments	1000 checks

Pattern observation: The work grows directly with the number of segments Kafka must check.

Final Time Complexity

Time Complexity: O(n)

This means the time Kafka spends checking retention grows linearly with the number of data segments.

Common Mistake

[X] Wrong: "Kafka checks only a few segments, so retention checks are always fast."

[OK] Correct: If there are many partitions and segments, Kafka must check each one, so the work grows with data size.

Interview Connect

Understanding how Kafka's retention policies scale helps you explain system behavior and resource use clearly.

Self-Check

"What if Kafka used a more efficient index to track segments needing deletion? How would the time complexity change?"

Practice

1. What does the retention.ms setting control in Kafka?

easy

A. The maximum size of a Kafka topic

B. How long Kafka keeps data before deleting it

C. The number of partitions in a topic

D. The replication factor of a topic

Solution

1. Step 1: Understand retention.ms meaning

   retention.ms sets the time duration Kafka retains data before deletion.

2. Step 2: Compare with other options

   Other options relate to size, partitions, or replication, not time retention.

3. Final Answer:

   How long Kafka keeps data before deleting it -> Option B

4. Quick Check:

   retention.ms = time-based retention [OK]

Hint: Remember ms means milliseconds, so it's about time [OK]

Common Mistakes:

• Confusing retention.ms with retention.bytes
• Thinking it controls topic size
• Mixing it with partition count

2. Which of the following is the correct way to set a size-based retention policy in Kafka's topic configuration?

easy

A. "retention.bytes" = 1073741824

B. "retention.time" = 604800000

C. "retention.size" = 1073741824

D. "retention.ms" = 1073741824

Solution

1. Step 1: Identify correct property for size-based retention

   The correct property is retention.bytes for size limits.

2. Step 2: Check option values and names

   "retention.bytes" = 1073741824 uses retention.bytes with a size value (1GB). Others use wrong keys or time-based keys.

3. Final Answer:

   "retention.bytes" = 1073741824 -> Option A

4. Quick Check:

   Size retention uses retention.bytes [OK]

Hint: Size retention uses bytes, so look for retention.bytes [OK]

Common Mistakes:

• Using retention.time instead of retention.ms
• Using retention.size which is invalid
• Confusing retention.ms with size setting

3. Given a Kafka topic with retention.ms=60000 and retention.bytes=1048576, what happens when the topic data reaches 2MB before 60 seconds pass?

medium

A. Kafka waits until 60 seconds pass before deleting any data

B. Kafka deletes data only if both time and size limits are reached

C. Kafka deletes old data immediately because size limit is reached

D. Kafka ignores retention settings and keeps all data

Solution

1. Step 1: Understand retention.ms and retention.bytes interaction

   Kafka deletes data when either time or size limit is reached, whichever comes first.

2. Step 2: Analyze given values

   Size limit is 1MB, data reached 2MB before 60 seconds, so size limit triggers deletion immediately.

3. Final Answer:

   Kafka deletes old data immediately because size limit is reached -> Option C

4. Quick Check:

   Retention triggers on earliest limit reached [OK]

Hint: Retention deletes when time OR size limit is reached [OK]

Common Mistakes:

• Thinking both limits must be reached to delete
• Assuming time limit always overrides size
• Ignoring size limit when time not reached

4. You set retention.ms to a negative value in Kafka topic config. What is the likely outcome?

medium

A. Kafka treats it as infinite retention (never deletes data)

B. Kafka throws a configuration error and refuses to start

C. Kafka deletes data immediately after creation

D. Kafka uses default retention time instead

Solution

1. Step 1: Check Kafka behavior for negative retention.ms

   Kafka interprets negative retention.ms as infinite retention, meaning no data deletion.

2. Step 2: Confirm other options

   Kafka does not throw error or delete immediately; it does not revert to default automatically.

3. Final Answer:

   Kafka treats it as infinite retention (never deletes data) -> Option A

4. Quick Check:

   Negative retention.ms means infinite retention [OK]

Hint: Negative retention.ms disables deletion, keeps data forever [OK]

Common Mistakes:

• Expecting an error on negative value
• Assuming immediate deletion
• Thinking default value applies automatically

5. You want to configure a Kafka topic to keep data for 2 hours or up to 500MB, whichever limit is reached first. Which configuration is correct?

hard

A. "retention.ms"=7200000 only, size limit is not needed

B. "retention.ms"=7200000 and "retention.bytes"=5000000000

C. "retention.ms"=120 and "retention.bytes"=524288000

D. "retention.ms"=7200000 and "retention.bytes"=524288000

Solution

1. Step 1: Convert 2 hours to milliseconds

   2 hours = 2 * 60 * 60 * 1000 = 7,200,000 ms.

2. Step 2: Convert 500MB to bytes

   500MB = 500 * 1024 * 1024 = 524,288,000 bytes.

3. Step 3: Match values to options

   "retention.ms"=7200000 and "retention.bytes"=524288000 matches both correct values; others have wrong size or time values.

4. Final Answer:

   "retention.ms"=7200000 and "retention.bytes"=524288000 -> Option D

5. Quick Check:

   2 hours = 7200000 ms, 500MB = 524288000 bytes [OK]

Hint: Convert hours to ms and MB to bytes carefully [OK]

Common Mistakes:

• Using seconds instead of milliseconds for retention.ms
• Confusing MB with bytes without conversion
• Setting only one limit when both are needed