Offset management in Kafka - Step-by-Step Execution

Process Flow - Offset management

Consumer reads message

↓

Process message

↓

Commit offset

↓

Next message read using committed offset

↓

Repeat

This flow shows how a Kafka consumer reads messages, processes them, commits the offset, and then reads the next message starting from the committed offset.

Execution Sample

Kafka

consumer.subscribe(['topic'])
for message in consumer:
    process(message)
    consumer.commit()

This code subscribes to a Kafka topic, processes each message, and commits the offset after processing.

Process Table

Step	Action	Offset Read	Message Processed	Offset Committed	Next Offset to Read
1	Start consuming	0	No	No	0
2	Read message	0	Message at offset 0	No	0
3	Process message	0	Message at offset 0	No	0
4	Commit offset	0	Message at offset 0	1	1
5	Read message	1	Message at offset 1	1	1
6	Process message	1	Message at offset 1	1	1
7	Commit offset	1	Message at offset 1	2	2
8	Read message	2	Message at offset 2	2	2
9	Process message	2	Message at offset 2	2	2
10	Commit offset	2	Message at offset 2	3	3
11	Stop consuming	3	No	3	3

💡 Consumer stops after processing and committing offset 2; next offset 3 is not read.

Status Tracker

Variable	Start	After Step 4	After Step 7	After Step 10	Final
Offset Read	0	1	2	3	3
Offset Committed	No	1	2	3	3
Next Offset to Read	0	1	2	3	3

Key Moments - 3 Insights

Why does the consumer commit the offset after processing the message?

Committing the offset after processing ensures that if the consumer restarts, it will resume from the next unprocessed message, avoiding duplicates or data loss. See steps 3 and 4 in the execution_table.

What happens if the consumer reads a message but does not commit the offset?

If the offset is not committed, on restart the consumer will re-read the same message, causing duplicate processing. This is shown between steps 5 and 6 where offset committed is still 1.

Why is the 'Next Offset to Read' always one more than the 'Offset Committed'?

Because Kafka consumers read messages starting from the last committed offset plus one, ensuring continuous processing without overlap. See the progression in the variable_tracker.

Visual Quiz - 3 Questions

Look at the execution_table, what is the 'Offset Committed' after step 7?

A 0

B 2

C 1

D 3

💡 Hint

Check the 'Offset Committed' column at step 7 in the execution_table.

At which step does the consumer first process the message at offset 2?

A Step 8

B Step 10

C Step 9

D Step 11

💡 Hint

Look at the 'Message Processed' column for offset 2 in the execution_table.

If the consumer never commits offsets, what will happen when it restarts?

A It will re-read messages from the beginning or last committed offset

B It will skip messages already processed

C It will start reading from the last committed offset

D It will stop consuming messages

💡 Hint

Refer to the key_moments explanation about committing offsets and duplicate processing.

Concept Snapshot

Kafka offset management:
- Consumer reads messages from a topic partition.
- After processing, consumer commits the offset.
- Committed offset marks the last processed message.
- On restart, consumer resumes from committed offset + 1.
- Proper offset commit avoids duplicates or data loss.

Full Transcript

This visual execution shows how Kafka consumers manage offsets. The consumer reads a message at a given offset, processes it, then commits that offset. Committing means the consumer tells Kafka it has successfully handled messages up to that offset. The next message read will start from the committed offset plus one. If the consumer stops and restarts, it resumes from the last committed offset, ensuring no messages are missed or processed twice. The execution table traces each step, showing the offset read, message processed, offset committed, and the next offset to read. The variable tracker summarizes how these values change over time. Key moments clarify why committing after processing is important and what happens if offsets are not committed. The quiz tests understanding of these steps and their effects. This helps beginners see the flow of offset management clearly and avoid common mistakes.