At-most-once delivery in Kafka - Commands & Configuration

Introduction

At-most-once delivery means messages are delivered zero or one time to consumers. This avoids duplicates but may lose some messages if failures happen.

When you want to avoid processing the same message twice even if some messages get lost

When occasional message loss is acceptable but duplicates cause big problems

When your system can tolerate missing data but cannot tolerate repeated data

When you want the simplest message delivery with minimal overhead

When you do not need guaranteed message processing but want fast throughput

Commands

This command starts a producer to send messages to the topic named example-topic on the Kafka broker running locally.

Terminal

kafka-console-producer --broker-list localhost:9092 --topic example-topic

Expected Output

No output (command runs silently)

→

--broker-list - Specifies the Kafka broker address to connect to

→

--topic - Specifies the topic to send messages to

This command starts a consumer that reads messages from example-topic from the beginning with auto-commit disabled, simulating at-most-once by disabling commits.

Terminal

kafka-console-consumer --bootstrap-server localhost:9092 --topic example-topic --from-beginning --enable-auto-commit false

Expected Output

First message

Second message

Third message

→

--bootstrap-server - Specifies the Kafka broker address to connect to

→

--topic - Specifies the topic to consume messages from

→

--enable-auto-commit - Disables automatic offset commits to avoid duplicate processing

This command shows the current offset positions for the consumer group example-group to verify message consumption state.

Terminal

kafka-consumer-groups --bootstrap-server localhost:9092 --group example-group --describe

Expected Output

TOPIC          PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG  CONSUMER-ID  HOST  CLIENT-ID

example-topic  0          3               3               0    consumer-1   /127.0.0.1  consumer-1

→

--group - Specifies the consumer group to describe

Key Concept

If you remember nothing else from this pattern, remember: at-most-once delivery means messages may be lost but never duplicated.

Common Mistakes

Enabling auto-commit in the consumer when trying to achieve at-most-once delivery

Auto-commit can cause offsets to be committed before processing, leading to message loss or duplicates if the consumer crashes

Disable auto-commit and manage offsets carefully to ensure messages are processed zero or one time

Not understanding that at-most-once can lose messages

Assuming all messages will be delivered can cause data loss in critical systems

Use at-most-once only when occasional message loss is acceptable

Summary

Use kafka-console-producer to send messages to a topic.

Use kafka-console-consumer with auto-commit disabled to consume messages at-most-once.

Check consumer group offsets with kafka-consumer-groups to monitor consumption.

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