Group coordinator in Kafka - Step-by-Step Execution

Process Flow - Group coordinator

Start Consumer Group

↓

Join Group Coordinator

↓

Coordinator Assigns Partitions

↓

Consumer Polls Messages

↓

Heartbeat to Coordinator

↓

Rebalance if Needed

↓

Continue Polling or Leave Group

The group coordinator manages consumer group membership, assigns partitions, and handles rebalances to ensure smooth message consumption.

Execution Sample

Kafka

consumer = KafkaConsumer('topic', group_id='group1')
for message in consumer:
    print(message.value)

This code creates a consumer in a group and continuously polls messages from assigned partitions.

Process Table

Step	Action	Coordinator Response	Consumer State	Output
1	Consumer starts and sends JoinGroup request	Coordinator registers consumer in group	Joining group	None
2	Coordinator assigns partitions to consumer	Sends assignment to consumer	Assigned partitions	None
3	Consumer polls messages from assigned partitions	No direct response	Consuming messages	Message values printed
4	Consumer sends heartbeat to coordinator	Acknowledges consumer is alive	Maintains membership	None
5	Another consumer joins group	Triggers rebalance	Rebalancing	None
6	Coordinator reassigns partitions	Sends new assignments	Partitions reassigned	None
7	Consumer continues polling with new assignments	No direct response	Consuming messages	Message values printed
8	Consumer leaves group	Removes consumer from group	Left group	None
9	Coordinator triggers final rebalance	Reassigns partitions to remaining consumers	Updated assignments	None

💡 Consumer leaves group or application stops, ending message consumption.

Status Tracker

Variable	Start	After Step 2	After Step 5	After Step 6	Final
Consumer State	Not started	Assigned partitions	Rebalancing	Partitions reassigned	Left group
Coordinator Group Members	Empty	1 consumer	2 consumers	2 consumers with new assignments	1 consumer

Key Moments - 3 Insights

Why does the consumer enter a rebalancing state after a new consumer joins?

When a new consumer joins, the coordinator must redistribute partitions to balance load, causing rebalancing as shown in step 5 of the execution_table.

What happens if the consumer stops sending heartbeats?

The coordinator assumes the consumer is dead and triggers a rebalance to assign its partitions to others, maintaining group health (implied between steps 4 and 5).

How does the coordinator know which partitions to assign?

The coordinator uses the group membership and partition info to assign partitions evenly among consumers, as seen in step 2 and step 6.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the consumer receive its partition assignment?

A Step 1

B Step 3

C Step 2

D Step 5

💡 Hint

Check the 'Coordinator Response' column for 'Sends assignment to consumer' in the execution_table.

According to variable_tracker, what is the consumer state after step 5?

A Assigned partitions

B Rebalancing

C Consuming messages

D Left group

💡 Hint

Look at the 'Consumer State' row under 'After Step 5' in variable_tracker.

If the consumer stops sending heartbeats, what will the coordinator most likely do next?

A Trigger a rebalance to remove the consumer

B Ignore and continue as normal

C Assign more partitions to the consumer

D Send a message to the consumer

💡 Hint

Refer to key_moments about heartbeat and rebalance behavior.

Concept Snapshot

Group Coordinator manages consumer group membership.
Consumers join group and get partition assignments.
Consumers send heartbeats to stay in group.
Coordinator triggers rebalance on membership changes.
Partitions are reassigned to balance load.
Consumers poll messages from assigned partitions.

Full Transcript

The group coordinator in Kafka manages the consumer group lifecycle. When a consumer starts, it sends a join request to the coordinator. The coordinator registers the consumer and assigns partitions to it. The consumer then polls messages from these partitions. To maintain membership, the consumer sends heartbeats to the coordinator. If a new consumer joins or one leaves, the coordinator triggers a rebalance to redistribute partitions evenly. This ensures all messages are consumed efficiently. If a consumer stops sending heartbeats, the coordinator assumes it is dead and reassigns its partitions to others. This process keeps the group healthy and balanced.

Practice

1. What is the main role of the group coordinator in Kafka consumer groups?

easy

A. It manages the membership and partition assignments of consumers in a group.

B. It stores all messages produced to Kafka topics.

C. It handles the replication of Kafka brokers.

D. It monitors the health of Kafka brokers.

Solution

1. Step 1: Understand the group coordinator's function

   The group coordinator is responsible for managing consumer group membership and partition assignments.

2. Step 2: Differentiate from other Kafka components

   Storing messages, replication, and broker health are handled by other Kafka components, not the group coordinator.

3. Final Answer:

   It manages the membership and partition assignments of consumers in a group. -> Option A

4. Quick Check:

   Group coordinator = manages consumer group membership [OK]

Hint: Group coordinator manages consumers, not brokers or data storage [OK]

Common Mistakes:

• Confusing group coordinator with Kafka broker
• Thinking it stores messages
• Mixing it with replication controller

2. Which configuration must be set in a Kafka consumer to join a consumer group?

easy

A. bootstrap.servers

B. group.id

C. auto.offset.reset

D. key.deserializer

Solution

1. Step 1: Identify the configuration for group membership

   The group.id setting defines the consumer group the consumer belongs to.

2. Step 2: Understand other configurations

   bootstrap.servers sets Kafka servers, auto.offset.reset controls offset behavior, and key.deserializer handles message key decoding.

3. Final Answer:

   group.id -> Option B

4. Quick Check:

   Set group.id to join a consumer group [OK]

Hint: Set group.id to join a consumer group in Kafka [OK]

Common Mistakes:

• Confusing bootstrap.servers with group.id
• Using auto.offset.reset to join group
• Not setting group.id at all

3. Given the following Kafka consumer code snippet, what will happen when two consumers with the same group.id subscribe to the same topic with 4 partitions?

consumer1 = KafkaConsumer('my-topic', group_id='group1')
consumer2 = KafkaConsumer('my-topic', group_id='group1')

medium

A. Each consumer will receive all messages from all partitions.

B. Only one consumer will receive messages; the other will be idle.

C. The consumers will share the partitions so each gets a subset of messages.

D. The consumers will cause a conflict and fail to consume.

Solution

1. Step 1: Understand consumer group behavior

   Consumers in the same group share partitions so that each partition is consumed by only one consumer.

2. Step 2: Apply to given scenario

   With 4 partitions and 2 consumers in the same group, partitions will be divided between them, each getting a subset.

3. Final Answer:

   The consumers will share the partitions so each gets a subset of messages. -> Option C

4. Quick Check:

   Same group.id means partition sharing [OK]

Hint: Same group.id consumers share partitions, not duplicate messages [OK]

Common Mistakes:

• Thinking each consumer gets all messages
• Assuming conflict causes failure
• Believing only one consumer works

4. You have a Kafka consumer group but notice that one consumer is not receiving any messages even though the topic has many partitions. What is a likely cause related to the group coordinator?

medium

A. The topic has no messages to consume.

B. The group coordinator failed and was not re-elected.

C. The consumer has a different group.id than the others.

D. The consumer is assigned zero partitions due to group rebalancing.

Solution

1. Step 1: Understand partition assignment by group coordinator

   The group coordinator assigns partitions to consumers; sometimes a consumer may get zero partitions after rebalancing.

2. Step 2: Analyze the symptom

   If a consumer is in the group but gets no partitions, it won't receive messages even if the topic has many partitions.

3. Final Answer:

   The consumer is assigned zero partitions due to group rebalancing. -> Option D

4. Quick Check:

   Zero partition assignment means no messages for that consumer [OK]

Hint: Zero partitions assigned means consumer gets no messages [OK]

Common Mistakes:

• Assuming consumer left group due to different group.id
• Thinking group coordinator failure stops all consumers
• Ignoring partition assignment in rebalancing

5. You want to ensure smooth failover in a Kafka consumer group when one consumer crashes. How does the group coordinator help achieve this?

hard

A. It automatically detects the failure and triggers a rebalance to assign partitions to remaining consumers.

B. It stores the crashed consumer's messages until it recovers.

C. It restarts the crashed consumer automatically.

D. It duplicates messages to all consumers to avoid data loss.

Solution

1. Step 1: Understand group coordinator's role in failure

   The group coordinator monitors consumer membership and triggers rebalancing when a consumer leaves or crashes.

2. Step 2: Explain failover mechanism

   On failure detection, the coordinator reassigns partitions to remaining consumers to continue processing without data loss.

3. Final Answer:

   It automatically detects the failure and triggers a rebalance to assign partitions to remaining consumers. -> Option A

4. Quick Check:

   Group coordinator triggers rebalance on consumer failure [OK]

Hint: Group coordinator triggers rebalance on consumer failure [OK]

Common Mistakes:

• Thinking it stores messages for crashed consumers
• Assuming it restarts consumers
• Believing it duplicates messages to all consumers