Consumer poll loop in Kafka - Step-by-Step Execution

Process Flow - Consumer poll loop

Start Consumer

↓

Poll for messages

↓

Are messages received?

No→Wait and Poll again

Yes↓

Process each message

↓

Commit offsets

↓

Loop back to Poll

The consumer starts, polls messages in a loop, processes them if any, commits offsets, then polls again.

Execution Sample

Kafka

consumer = KafkaConsumer(bootstrap_servers=['localhost:9092'], enable_auto_commit=False)
consumer.subscribe(['topic'])
while True:
    records = consumer.poll(timeout_ms=1000)
    for record_list in records.values():
        for record in record_list:
            process(record)
    consumer.commit()

This code continuously polls messages from a Kafka topic, processes them, and commits offsets.

Process Table

Step	Action	Poll Result	Process Messages	Commit Offsets	Loop Back
1	Start consumer and poll	No messages	No processing	No commit	Poll again
2	Poll messages	Received 2 messages	Process message 1	No commit yet	Continue processing
3	Process message 2	Same 2 messages	Process message 2	No commit yet	After processing all
4	Commit offsets	No new poll	No processing	Offsets committed	Poll again
5	Poll messages	No messages	No processing	No commit	Poll again
6	Poll messages	Received 1 message	Process message 1	No commit yet	Continue processing
7	Commit offsets	No new poll	No processing	Offsets committed	Poll again
8	Poll messages	No messages	No processing	No commit	Poll again
Exit	Stop condition met (not shown in code)	Stop polling	Stop processing	Stop committing	Exit loop

💡 Loop runs indefinitely unless stopped externally; here exit is hypothetical.

Status Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	After 6	Final
records	empty	empty	2 messages	2 messages	empty	empty	1 message	empty
processed_messages	0	0	1	2	2	2	1	1
offsets_committed	false	false	false	false	true	true	true	true

Key Moments - 3 Insights

Why does the consumer poll again even if no messages are received?

Because the poll loop is continuous; when poll returns no messages (see Step 1 and 5), the loop waits and polls again to check for new messages.

When are offsets committed in the loop?

Offsets are committed only after all messages from the current poll are processed (see Step 4 and 7), ensuring processed messages are marked.

Does the poll method return messages immediately every time?

No, poll waits up to the timeout and may return no messages if none are available (see Step 1 and 5).

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'processed_messages' after Step 3?

A 2

B 1

C 0

D 3

💡 Hint

Check the variable_tracker row for 'processed_messages' at After 3.

At which step does the consumer commit offsets for the first time?

A Step 2

B Step 4

C Step 3

D Step 1

💡 Hint

Look at the 'Commit Offsets' column in the execution_table.

If the poll always returned no messages, how would the 'processed_messages' variable change?

A It would keep increasing

B It would reset to 0 each loop

C It would stay at 0

D It would become negative

💡 Hint

Refer to variable_tracker and execution_table rows where poll returns no messages.

Concept Snapshot

Consumer poll loop syntax:
while True:
  records = consumer.poll(timeout_ms=1000)
  for record_list in records.values():
    for record in record_list:
      process(record)
  consumer.commit()

Behavior:
- Poll waits for messages
- Processes all received messages
- Commits offsets after processing
- Loops continuously to consume new messages

Full Transcript

This visual execution shows how a Kafka consumer uses a poll loop to receive messages. The consumer starts and polls for messages. If no messages arrive, it polls again. When messages arrive, it processes each one, then commits offsets to mark progress. This repeats indefinitely. Variables like 'records', 'processed_messages', and 'offsets_committed' change step by step. Key moments clarify why polling repeats without messages and when commits happen. The quiz tests understanding of these steps and variable changes.