Static group membership in Kafka - Step-by-Step Execution

Process Flow - Static group membership

Start Consumer

↓

Join Group Request

↓

Static Member ID Provided?

No→Assign Dynamic Member ID

|Yes↓

Join Group with Static Member ID

↓

Group Coordinator Accepts

↓

Consumer Joins Group

↓

Consumer Maintains Session

↓

Rebalance Triggered?

No→Continue Processing

Yes↓

Static Member Rejoins with Same ID

↓

Group Stabilizes Without Losing Member

↓

Continue Processing

The consumer joins a group using a static member ID to keep membership stable across restarts, avoiding unnecessary rebalances.

Execution Sample

Kafka

consumerProps.put(ConsumerConfig.GROUP_ID_CONFIG, "my-group");
consumerProps.put(ConsumerConfig.GROUP_INSTANCE_ID_CONFIG, "consumer-1");
KafkaConsumer<String, String> consumer = new KafkaConsumer<>(consumerProps);
consumer.subscribe(Collections.singletonList("my-topic"));
consumer.poll(Duration.ofMillis(100));

This code creates a Kafka consumer with a static group instance ID to join a consumer group with static membership.

Process Table

Step	Action	Static Member ID Provided?	Group Coordinator Response	Result
1	Consumer starts and sends JoinGroup request	Yes (consumer-1)	Accepts static member	Consumer joins group with static ID
2	Consumer polls messages	Yes (consumer-1)	Maintains session	Consumer processes messages
3	Consumer restarts and re-joins group	Yes (consumer-1)	Recognizes static member	No rebalance triggered, session continues
4	Another consumer joins with dynamic ID	No	Triggers rebalance	Group rebalances, static member remains stable
5	Static member leaves group	Yes (consumer-1)	Removes member	Group rebalances to exclude static member

💡 Execution stops when consumer leaves group or application ends.

Status Tracker

Variable	Start	After Step 1	After Step 3	After Step 4	Final
memberId	null	consumer-1	consumer-1	consumer-1	null
groupState	empty	joined	joined	rebalancing	left
rebalanceNeeded	false	false	false	true	false

Key Moments - 3 Insights

Why does the group not rebalance when the static member restarts?

Because the static member rejoins with the same member ID (see execution_table step 3), the coordinator keeps the member stable and avoids rebalance.

What happens if a consumer joins without a static member ID?

The group coordinator treats it as a dynamic member, which can trigger a rebalance (see execution_table step 4).

Why is the memberId variable null at the start and final steps?

At start, the consumer has not joined yet, so memberId is null; at final, after leaving the group, memberId resets to null (see variable_tracker).

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what does the group coordinator do when the static member rejoins?

A Triggers a rebalance

B Rejects the member

C Recognizes static member and avoids rebalance

D Assigns a new dynamic member ID

💡 Hint

Check the 'Group Coordinator Response' column at step 3 in execution_table

According to variable_tracker, what is the value of 'rebalanceNeeded' after step 4?

A false

B true

C null

D undefined

💡 Hint

Look at the 'rebalanceNeeded' row and the 'After Step 4' column in variable_tracker

If the static member ID was not provided at step 1, what would likely happen?

A Consumer joins as dynamic member, possibly triggering rebalance

B Group coordinator rejects the join

C Consumer joins with static ID anyway

D Consumer cannot join the group

💡 Hint

Refer to execution_table step 4 where a consumer without static ID triggers rebalance

Concept Snapshot

Static group membership in Kafka:
- Use GROUP_INSTANCE_ID_CONFIG to set static member ID
- Static members keep same ID across restarts
- Avoids unnecessary group rebalances
- Coordinator recognizes static IDs to maintain stability
- Helps improve consumer group stability and performance

Full Transcript

Static group membership in Kafka allows consumers to join a group with a fixed member ID. This ID is set using the GROUP_INSTANCE_ID_CONFIG property. When a consumer restarts, it uses the same static ID to rejoin the group. The group coordinator recognizes this and avoids triggering a rebalance, keeping the group stable. If a consumer joins without a static ID, it is treated as dynamic and may cause rebalances. Variables like memberId track the consumer's identity, and groupState tracks the membership status. This feature improves consumer group stability by reducing unnecessary rebalances.