Consumer offset commit strategies in Kafka - Step-by-Step Execution

Process Flow - Consumer offset commit strategies

Start consuming messages

↓

Process message

↓

Decide commit strategy

↓

Auto commit

↓

Commit offset

↓

Continue consuming

This flow shows how a Kafka consumer processes messages and commits offsets using different strategies: auto, synchronous, or asynchronous commits.

Execution Sample

Kafka

consumer.subscribe(['topic'])
for message in consumer:
    process(message)
    consumer.commit()  # sync commit
    # or consumer.commit_async()  # async commit

A Kafka consumer subscribes to a topic, processes each message, and commits the offset synchronously or asynchronously.

Process Table

Step	Message Offset	Processing	Commit Strategy	Commit Action	Next Offset
1	0	Processed message 0	Auto commit disabled	No commit yet	1
2	1	Processed message 1	Sync commit	Commit offset 1 synchronously	2
3	2	Processed message 2	Async commit	Commit offset 2 asynchronously	3
4	3	Processed message 3	Sync commit	Commit offset 3 synchronously	4
5	-	No more messages	-	Stop consuming	-

💡 No more messages to consume, consumer stops.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
current_offset	None	0	1	2	3	3
commit_status	None	No commit	Committed sync	Committed async	Committed sync	Committed sync

Key Moments - 2 Insights

Why does the offset sometimes commit synchronously and sometimes asynchronously?

The commit strategy depends on the method called: commit() blocks until Kafka confirms, while commit_async() sends the commit request without waiting. See execution_table rows 2 and 3.

What happens if auto commit is disabled?

Offsets are not committed automatically after processing messages. The consumer must call commit() or commit_async() manually to save progress, as shown in step 1 where no commit occurs.

Visual Quiz - 3 Questions

Look at the execution_table, what is the commit action at step 3?

A Commit offset 2 synchronously

B Commit offset 2 asynchronously

C No commit performed

D Commit offset 1 asynchronously

💡 Hint

Check the 'Commit Action' column in execution_table row 3.

At which step does the consumer commit offset 1 synchronously?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at the 'Commit Strategy' and 'Commit Action' columns in execution_table.

If auto commit was enabled, how would the commit actions change in the table?

A Only async commits would be used

B No commits would happen at all

C Commits would happen automatically after each message without explicit calls

D Only sync commits would be used

💡 Hint

Auto commit means Kafka commits offsets automatically after processing messages.

Concept Snapshot

Kafka consumers track message offsets to know what was processed.
Offsets can be committed automatically or manually.
Manual commits can be synchronous (blocking) or asynchronous (non-blocking).
Choosing the right commit strategy balances reliability and performance.
Auto commit is easy but less precise; manual commit gives control.

Full Transcript

This visual execution shows how Kafka consumers handle offset commits. The consumer reads messages one by one, processes them, and commits offsets to Kafka to mark progress. There are three main commit strategies: auto commit, synchronous commit, and asynchronous commit. Auto commit happens automatically at intervals, but here it is disabled, so commits are manual. Synchronous commit waits for Kafka to confirm the offset is saved before continuing, ensuring reliability but slowing down processing. Asynchronous commit sends the commit request without waiting, improving speed but risking lost commits if the consumer crashes. The execution table traces each step: processing a message, choosing commit strategy, committing offset, and moving to the next message. The variable tracker shows how the current offset and commit status change over time. Key moments clarify why commit methods differ and what happens if auto commit is disabled. The quiz tests understanding of commit actions at specific steps and the effect of enabling auto commit. This helps beginners see how offset commits work in practice and why choosing the right strategy matters.