Idempotent producer in Kafka - Step-by-Step Execution

Process Flow - Idempotent producer

Start Producer

↓

Send Message

↓

Assign Sequence Number

↓

Broker Receives

↓

Check Sequence Number

↓

Duplicate

↓

Ignore

↓

Producer Receives Ack

↓

Continue Sending

The producer sends messages with sequence numbers; the broker checks for duplicates and only stores unique messages, ensuring no duplicates on retries.

Execution Sample

Kafka

producer = KafkaProducer(enable_idempotence=True)
producer.send('topic', b'message1')
producer.send('topic', b'message1')  # retry
producer.flush()

This code sends the same message twice with idempotence enabled, so the broker stores it only once.

Process Table

Step	Action	Sequence Number	Broker Check	Broker Action	Producer Output
1	Send message1	1	Is seq 1 duplicate?	No - store message	Ack for seq 1
2	Retry send message1	1	Is seq 1 duplicate?	Yes - ignore duplicate	Ack for seq 1
3	Flush producer	-	-	-	All messages confirmed

💡 Producer stops after flush; broker ensures message1 stored once despite retry

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
sequence_number	0	1	1	1
broker_stored_messages	[]	[message1]	[message1]	[message1]
producer_acknowledged	False	True	True	True

Key Moments - 3 Insights

Why does the broker ignore the second message with the same sequence number?

Because the broker checks the sequence number (see execution_table step 2) and detects it as a duplicate, so it ignores storing it again.

Does the producer get an acknowledgment for the retry message?

Yes, the producer receives the same acknowledgment for the sequence number (execution_table step 2), confirming the message was accepted.

What happens if idempotence is not enabled?

Without idempotence, the broker would store duplicates on retries, causing repeated messages; here, idempotence prevents that.

Visual Quiz - 3 Questions

Look at the execution table, what is the broker's action at step 2?

A Ignore the duplicate message

B Store the message again

C Send an error to producer

D Increase sequence number

💡 Hint

Check the 'Broker Action' column at step 2 in the execution_table

At which step does the producer receive acknowledgment for the first message?

A Step 3

B Step 2

C Step 1

D No acknowledgment received

💡 Hint

Look at the 'Producer Output' column in execution_table step 1

If the producer did not enable idempotence, what would change in the broker stored messages after step 2?

A No change, still one message

B Two copies of the same message stored

C Broker would reject the second message

D Sequence number would reset

💡 Hint

Refer to key_moments explanation about duplicates without idempotence

Concept Snapshot

Idempotent producer in Kafka:
- Sends messages with unique sequence numbers
- Broker checks sequence to avoid duplicates
- Retries do not create duplicate messages
- Ensures exactly-once delivery on producer side
- Enable with 'enable_idempotence=True' in producer config

Full Transcript

An idempotent producer in Kafka sends messages with sequence numbers. The broker checks these numbers to detect duplicates. If a message with the same sequence number arrives again, the broker ignores it to avoid duplicates. The producer receives acknowledgments for messages once stored. This ensures that even if the producer retries sending a message, the broker stores it only once. This behavior is enabled by setting 'enable_idempotence' to true in the producer configuration. The execution table shows the steps: sending the first message, retrying the same message, and flushing the producer. The variable tracker shows how sequence numbers and stored messages change. Key moments clarify why duplicates are ignored and how acknowledgments work. The visual quiz tests understanding of broker actions and producer acknowledgments.