Group coordinator in Kafka - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Kafka consumer with a group coordinator.

Kafka

Properties props = new Properties();
props.put("bootstrap.servers", "localhost:9092");
props.put("group.id", [1]);
props.put("key.deserializer", "org.apache.kafka.common.serialization.StringDeserializer");
props.put("value.deserializer", "org.apache.kafka.common.serialization.StringDeserializer");
KafkaConsumer<String, String> consumer = new KafkaConsumer<>(props);

Drag options to blanks, or click blank then click option'

A"my-group"

B"localhost"

C"consumer"

D"topic1"

Attempts:

3 left

💡 Hint

Common Mistakes

Using the broker address instead of the group id

Using the topic name as group id

Leaving group.id empty

The group coordinator is identified by the group.id property, which should be a string like "my-group".

2fill in blank

medium

Complete the code to subscribe the consumer to a topic.

Kafka

consumer.[1](Collections.singletonList("my-topic"));

Drag options to blanks, or click blank then click option'

AcommitSync

Bassign

Csubscribe

Dpoll

Attempts:

3 left

💡 Hint

Common Mistakes

Using assign instead of subscribe

Calling poll before subscribing

Using commitSync to subscribe

The subscribe method is used to subscribe the consumer to a list of topics.

3fill in blank

hard

Fix the error in the code to poll messages from the consumer.

Kafka

ConsumerRecords<String, String> records = consumer.[1](Duration.ofMillis(100));
for (ConsumerRecord<String, String> record : records) {
    System.out.println(record.value());
}

Drag options to blanks, or click blank then click option'

Aassign

Bsubscribe

CcommitSync

Dpoll

Attempts:

3 left

💡 Hint

Common Mistakes

Using subscribe instead of poll to get messages

Calling commitSync before polling

Using assign instead of poll

The poll method retrieves messages from the broker within the specified timeout.

4fill in blank

hard

Fill both blanks to commit offsets synchronously after processing.

Kafka

consumer.[1](Duration.ofMillis(100));
try {
    consumer.[2]();
} catch (Exception e) {
    e.printStackTrace();
}

Drag options to blanks, or click blank then click option'

AcommitSync

Bpoll

Cclose

Dsubscribe

Attempts:

3 left

💡 Hint

Common Mistakes

Committing before polling

Using close instead of commitSync

Not handling exceptions during commit

First, poll to get messages, then commitSync to commit offsets synchronously.

5fill in blank

hard

Fill all three blanks to create a consumer, subscribe, and poll messages.

Kafka

Properties props = new Properties();
props.put("bootstrap.servers", "localhost:9092");
props.put("group.id", [1]);
props.put("key.deserializer", "org.apache.kafka.common.serialization.StringDeserializer");
props.put("value.deserializer", "org.apache.kafka.common.serialization.StringDeserializer");
KafkaConsumer<String, String> consumer = new KafkaConsumer<>(props);
consumer.[2](Collections.singletonList("my-topic"));
ConsumerRecords<String, String> records = consumer.[3](Duration.ofMillis(100));

Drag options to blanks, or click blank then click option'

A"group1"

Bsubscribe

Cpoll

D"topic1"

Attempts:

3 left

💡 Hint

Common Mistakes

Using topic name as group.id

Calling poll before subscribe

Using assign instead of subscribe

Set group.id to "group1", subscribe to the topic, then poll messages.

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