At-most-once delivery in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does At-most-once delivery mean in message systems like Kafka?

It means each message is delivered zero or one time. Messages might be lost but never duplicated.

intermediate

How does Kafka achieve at-most-once delivery?

By committing the message offset before processing, so if a failure happens, some messages might be skipped but never repeated.

beginner

What is a risk of at-most-once delivery?

Messages can be lost if a failure happens after committing the offset but before processing the message.

intermediate

Compare at-most-once and at-least-once delivery.

At-most-once: messages delivered zero or one time (no duplicates, possible loss).
At-least-once: messages delivered one or more times (no loss, possible duplicates).

beginner

Why might a system choose at-most-once delivery?

To prioritize speed and simplicity over guaranteed delivery, especially when losing some messages is acceptable.

In Kafka, what happens if you commit the offset before processing a message?

A Messages are duplicated.

B You get at-least-once delivery.

C You get exactly-once delivery.

D You get at-most-once delivery.

Committing offset before processing means messages might be skipped if failure occurs, so at-most-once delivery is achieved.

Which delivery guarantee allows message loss but no duplicates?

A At-most-once

B Exactly-once

C At-least-once

D None

At-most-once delivery can lose messages but never delivers duplicates.

What is a downside of at-most-once delivery?

A Messages may be duplicated.

B Messages may be lost.

C Processing is slower.

D It requires complex coordination.

At-most-once delivery risks losing messages if failures happen after offset commit.

If you want to avoid duplicates but can accept some message loss, which delivery mode fits best?

A At-most-once

B At-least-once

C Exactly-once

D No delivery

At-most-once delivery avoids duplicates but may lose messages.

Which Kafka feature controls which messages a consumer has processed?

A Topic partition

B Producer ID

C Offset

D Broker

Offset tracks the position of the consumer in the message stream.

Explain in your own words what at-most-once delivery means and how Kafka can implement it.

Think about when the offset is saved and what happens if a failure occurs.

Describe the trade-offs between at-most-once and at-least-once delivery in Kafka.

Consider what happens if a failure occurs before or after processing.

Practice

1.

What does at-most-once delivery guarantee in Kafka messaging?

easy

A. Messages are sent at least once, possibly duplicated

B. Messages are sent exactly once with no loss

C. Messages are sent only once but some may be lost

D. Messages are sent multiple times intentionally

Solution

1. Step 1: Understand at-most-once delivery meaning

   At-most-once delivery means messages are sent once without retries, so duplicates are avoided but some messages might be lost.

2. Step 2: Compare with other delivery guarantees

   At-least-once allows duplicates, exactly-once avoids loss and duplicates, so only at-most-once fits the description of possible loss but no duplicates.

3. Final Answer:

   Messages are sent only once but some may be lost -> Option C

4. Quick Check:

   At-most-once = no duplicates, possible loss [OK]

Hint: At-most-once means no retries, so possible message loss [OK]

Common Mistakes:

• Confusing at-most-once with exactly-once delivery
• Assuming no messages are ever lost
• Thinking duplicates can occur in at-most-once

2.

Which Kafka producer configuration enables at-most-once delivery?

producer = KafkaProducer(acks=?, retries=? )

easy

A. acks=all, retries=5

B. acks=0, retries=0

C. acks=1, retries=3

D. acks=all, retries=0

Solution

1. Step 1: Identify settings for at-most-once

   At-most-once requires no retries and no acknowledgments, so acks=0 and retries=0 are needed.

2. Step 2: Check other options

   Other options enable retries or acknowledgments, which allow retries and possible duplicates, not at-most-once.

3. Final Answer:

   acks=0, retries=0 -> Option B

4. Quick Check:

   acks=0 & retries=0 = at-most-once [OK]

Hint: Set acks and retries to zero for at-most-once [OK]

Common Mistakes:

• Setting retries > 0 allows retries, not at-most-once
• Using acks=all causes waiting for confirmation
• Confusing acks=1 with acks=0

3.

Given the following Kafka producer code snippet, what is the expected delivery guarantee?

producer = KafkaProducer(acks=0, retries=0)
producer.send('topic', b'message')

medium

A. At-most-once delivery with possible message loss

B. No message will be sent

C. Exactly-once delivery with no duplicates

D. At-least-once delivery with possible duplicates

Solution

1. Step 1: Analyze producer settings

   With acks=0 and retries=0, the producer does not wait for acknowledgment and does not retry on failure.

2. Step 2: Determine delivery guarantee

   This means messages may be lost if sending fails, but duplicates won't occur, matching at-most-once delivery.

3. Final Answer:

   At-most-once delivery with possible message loss -> Option A

4. Quick Check:

   acks=0 & retries=0 = at-most-once [OK]

Hint: acks=0 and retries=0 means no retries, so at-most-once [OK]

Common Mistakes:

• Assuming messages are always delivered
• Confusing at-most-once with exactly-once
• Thinking duplicates can happen here

4.

Identify the error in this Kafka producer configuration for at-most-once delivery:

producer = KafkaProducer(acks=1, retries=0)
producer.send('topic', b'message')

medium

A. acks=1 causes waiting for leader ack, not at-most-once

B. retries=0 causes infinite retries

C. Missing enable.idempotence=True

D. Topic name must be uppercase

Solution

1. Step 1: Check acks setting

   acks=1 means the producer waits for leader acknowledgment, allowing retries and possible duplicates, not at-most-once.

2. Step 2: Verify retries and other settings

   Retries=0 disables retries, but acks=1 still waits for confirmation, so this is not pure at-most-once.

3. Final Answer:

   acks=1 causes waiting for leader ack, not at-most-once -> Option A

4. Quick Check:

   acks must be 0 for at-most-once [OK]

Hint: acks must be 0 for at-most-once delivery [OK]

Common Mistakes:

• Thinking retries=0 means no retries but ignoring acks effect
• Assuming idempotence is required for at-most-once
• Believing topic names must be uppercase

5.

You want to configure a Kafka producer for at-most-once delivery but also need to minimize message loss. Which combination of settings is best?

Options:
A) acks=1, retries=0
B) acks=0, retries=0
C) acks=0, retries=3
D) acks=all, retries=0

hard

A. acks=all, retries=0 (wait for all acks, no retries)

B. acks=0, retries=0 (pure at-most-once, possible loss)

C. acks=0, retries=3 (retries with no ack, risky duplicates)

D. acks=1, retries=0 (wait for ack, no retries, less loss)

Solution

1. Step 1: Understand trade-offs

   Pure at-most-once (acks=0, retries=0) risks message loss. Waiting for ack reduces loss but may not be pure at-most-once.

2. Step 2: Evaluate options

   acks=1, retries=0 (wait for ack, no retries, less loss) waits for leader ack but disables retries, reducing loss while avoiding duplicates, closest to at-most-once with less loss.

3. Final Answer:

   acks=1, retries=0 (wait for ack, no retries, less loss) -> Option D

4. Quick Check:

   acks=1 & retries=0 balances loss and duplicates [OK]

Hint: Wait for ack but disable retries to reduce loss in at-most-once [OK]

Common Mistakes:

• Choosing retries > 0 breaks at-most-once
• Ignoring ack setting impact on loss
• Assuming acks=all with no retries is at-most-once