Acknowledgment modes (acks=0, 1, all) in Kafka - Time & Space Complexity

Time Complexity: Acknowledgment modes (acks=0, 1, all)

O(n)

Understanding Time Complexity

When sending messages in Kafka, the acknowledgment mode controls how many confirmations the producer waits for before continuing.

We want to understand how the time to send messages changes with different acknowledgment settings.

Scenario Under Consideration

Analyze the time complexity of sending messages with different acknowledgment modes.

producer.send(record, new Callback() {
  public void onCompletion(RecordMetadata metadata, Exception e) {
    if (e != null) {
      // handle error
    }
  }
});

// acks can be set to 0, 1, or all in producer config

This code sends a message and waits for acknowledgments based on the configured mode.

Identify Repeating Operations

Look at what happens each time a message is sent.

• Primary operation: Sending a message and waiting for acknowledgments.
• How many times: Once per message sent.

How Execution Grows With Input

As the number of messages (n) grows, the time to send all messages depends on the acknowledgment mode.

Input Size (n)	Approx. Operations
10	10 sends, each with minimal to moderate wait
100	100 sends, each with minimal to moderate wait
1000	1000 sends, each with minimal to moderate wait

Pattern observation: The total time grows roughly linearly with the number of messages, but the wait time per message varies by acknowledgment mode.

Final Time Complexity

Time Complexity: O(n)

This means the time to send messages grows directly with how many messages you send, regardless of acknowledgment mode.

Common Mistake

[X] Wrong: "Using acks=0 means sending messages is instant and time doesn't grow with more messages."

[OK] Correct: Even with acks=0, sending each message takes some time, so total time still grows with the number of messages.

Interview Connect

Understanding how acknowledgment modes affect message sending time helps you explain trade-offs between speed and reliability in real systems.

Self-Check

What if we batch multiple messages together before sending? How would that affect the time complexity?

Practice

1. Which acks mode in Kafka provides the fastest message sending but with the least safety?

easy

A. acks=0

B. acks=1

C. acks=all

D. None of the above

Solution

1. Step 1: Understand acks=0 behavior

   This mode means the producer does not wait for any acknowledgment from the broker, so it sends messages fastest but with no guarantee of delivery.

2. Step 2: Compare with other modes

   acks=1 waits for leader confirmation, and acks=all waits for all replicas, both slower but safer.

3. Final Answer:

   acks=0 -> Option A

4. Quick Check:

   Fastest but least safe = acks=0 [OK]

Hint: No wait for confirmation means fastest mode is acks=0 [OK]

Common Mistakes:

• Confusing acks=0 with acks=1
• Thinking acks=all is fastest
• Assuming acks=0 waits for leader

2. Which of the following is the correct way to set the acknowledgment mode to wait for all replicas in Kafka producer configuration?

easy

A. "acks=1"

B. "acks=0"

C. "acks=all"

D. "ack=all"

Solution

1. Step 1: Recall correct property name and value

   The property is acks (plural), and to wait for all replicas, the value is all.

2. Step 2: Check options for syntax correctness

   "acks=all" uses correct key and value: "acks=all". "ack=all" has a typo "ack" instead of "acks".

3. Final Answer:

   "acks=all" -> Option C

4. Quick Check:

   Wait for all replicas = acks=all [OK]

Hint: Remember plural 'acks' and value 'all' for all replicas [OK]

Common Mistakes:

• Using 'ack' instead of 'acks'
• Confusing 'acks=1' with 'acks=all'
• Setting 'acks=0' for all replicas

3. Consider this Kafka producer code snippet:

props.put("acks", "1");
producer.send(record);
System.out.println("Message sent");

What does acks=1 guarantee before printing "Message sent"?

medium

A. Message is stored only in producer buffer

B. No guarantee; message may be lost

C. All replicas have confirmed the message

D. Leader broker has confirmed the message

Solution

1. Step 1: Understand acks=1 meaning

   This mode waits for the leader broker to confirm the message is received and written to its log.

2. Step 2: Compare with other options

   acks=0 gives no guarantee, acks=all waits for all replicas, and producer buffer storage is unrelated.

3. Final Answer:

   Leader broker has confirmed the message -> Option D

4. Quick Check:

   acks=1 means leader confirmation [OK]

Hint: acks=1 waits for leader confirmation only [OK]

Common Mistakes:

• Thinking acks=1 waits for all replicas
• Assuming no guarantee with acks=1
• Confusing producer buffer with broker confirmation

4. You have this Kafka producer configuration:

props.put("acks", "alll");

What is the problem with this configuration?

medium

A. Typo in the value; should be "all"

B. Typo in the key; should be "ack"

C. No problem; "alll" is valid

D. Should be an integer, not a string

Solution

1. Step 1: Check the value spelling

   The correct value for waiting all replicas is "all", but here it is misspelled as "alll" with an extra 'l'.

2. Step 2: Verify key and value types

   The key "acks" is correct and the value should be a string. So the problem is only the typo in the value.

3. Final Answer:

   Typo in the value; should be "all" -> Option A

4. Quick Check:

   Value must be "all", not "alll" [OK]

Hint: Check spelling of 'all' carefully in acks value [OK]

Common Mistakes:

• Assuming 'alll' is valid
• Changing key to 'ack' instead of 'acks'
• Using integer instead of string for acks

5. You want to ensure maximum data safety in Kafka producer but can tolerate some delay. Which acks setting should you use and why?

hard

A. acks=1 because leader confirmation is enough

B. acks=all because it waits for all replicas

C. acks=0 because it is fastest

D. acks=-1 because it disables acknowledgments

Solution

1. Step 1: Identify safety vs speed tradeoff

   acks=all waits for all replicas to confirm, ensuring maximum data safety but slower performance.

2. Step 2: Evaluate other options

   acks=0 is fastest but unsafe, acks=1 waits only for leader, and acks=-1 is invalid or equivalent to acks=all but less clear.

3. Final Answer:

   acks=all because it waits for all replicas -> Option B

4. Quick Check:

   Max safety = acks=all [OK]

Hint: Max safety means waiting for all replicas: acks=all [OK]

Common Mistakes:

• Choosing acks=0 for safety
• Confusing acks=-1 as disabling acknowledgments
• Thinking leader confirmation is max safety