Consumer lag monitoring in Kafka - Commands & Configuration

Introduction

When you use Kafka to send messages, consumers read these messages. Consumer lag monitoring helps you see if consumers are falling behind and not reading messages fast enough. This prevents delays and data loss.

When you want to check if your app reading messages from Kafka is keeping up with new messages.

When you notice delays in processing data from Kafka topics and want to find the cause.

When you want to alert your team if consumers stop reading messages for too long.

When you deploy a new consumer and want to verify it catches up with existing messages.

When you want to optimize consumer performance by understanding lag patterns.

Commands

This command shows the current lag of the consumer group named 'my-consumer-group'. It tells how many messages behind the consumer is for each partition.

Terminal

kafka-consumer-groups --bootstrap-server localhost:9092 --describe --group my-consumer-group

Expected Output

TOPIC           PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG  CONSUMER-ID                                    HOST            CLIENT-ID

my-topic       0          105             110             5    consumer-1-12345-67890                        /127.0.0.1      consumer-1

→

--bootstrap-server - Specifies the Kafka server address to connect to.

→

--describe - Shows detailed information about the consumer group.

→

--group - Specifies which consumer group to check.

This command lists all consumer groups in the Kafka cluster so you can find the group name to monitor.

Terminal

kafka-consumer-groups --bootstrap-server localhost:9092 --list

Expected Output

my-consumer-group

another-group

analytics-group

→

--bootstrap-server - Specifies the Kafka server address to connect to.

→

--list - Lists all consumer groups.

Key Concept

If you remember nothing else from this pattern, remember: consumer lag shows how far behind your app is in reading messages, so monitoring it helps keep data fresh and processing timely.

Common Mistakes

Using the wrong consumer group name in the command.

The command will show no data or errors because it cannot find that group.

Use 'kafka-consumer-groups --list' first to find the exact group name.

Checking lag without specifying the correct Kafka server address.

The command cannot connect and will fail or show no output.

Always use the correct --bootstrap-server flag with your Kafka server address.

Summary

Use 'kafka-consumer-groups --list' to find consumer groups in your Kafka cluster.

Use 'kafka-consumer-groups --describe --group <group-name>' to see lag details for a consumer group.

Monitoring consumer lag helps ensure your consumers keep up with message production and avoid delays.

Practice

1. What does consumer lag in Kafka indicate?

easy

A. The delay between the latest message produced and the message consumed

B. The number of consumers in a consumer group

C. The total number of messages produced to a topic

D. The size of the Kafka topic in bytes

Solution

1. Step 1: Understand consumer lag meaning

   Consumer lag measures how far behind a consumer is from the latest message produced in the topic partition.

2. Step 2: Differentiate from other metrics

   It is not about consumer count, total messages, or topic size, but about delay in consumption.

3. Final Answer:

   The delay between the latest message produced and the message consumed -> Option A

4. Quick Check:

   Consumer lag = delay behind latest message [OK]

Hint: Lag means delay between produced and consumed messages [OK]

Common Mistakes:

• Confusing lag with consumer count
• Thinking lag is topic size
• Mixing lag with total messages produced

2. Which command correctly shows consumer lag for a group named my-group?

easy

A. kafka-consumer-groups.sh --describe --group my-group

B. kafka-consumer-groups.sh --list --group my-group

C. kafka-topics.sh --describe --group my-group

D. kafka-producer-perf-test.sh --group my-group

Solution

1. Step 1: Identify correct command for consumer lag

   The command to describe consumer group lag is kafka-consumer-groups.sh --describe --group <group-name>.

2. Step 2: Eliminate incorrect commands

   --list lists groups but does not show lag; kafka-topics.sh is for topics, not groups; kafka-producer-perf-test.sh is unrelated.

3. Final Answer:

   kafka-consumer-groups.sh --describe --group my-group -> Option A

4. Quick Check:

   Describe group shows lag [OK]

Hint: Use --describe with --group to see lag [OK]

Common Mistakes:

• Using --list instead of --describe
• Confusing topic commands with consumer group commands
• Using producer commands for consumer lag

3. Given this output from kafka-consumer-groups.sh --describe --group my-group:

TOPIC           PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG  CONSUMER-ID
my-topic       0          100             105             5    consumer-1
my-topic       1          200             200             0    consumer-1

What is the total lag for the consumer group?

medium

A. 105

B. 5

C. 0

D. 205

Solution

1. Step 1: Identify lag per partition

   Partition 0 lag is 5, partition 1 lag is 0.

2. Step 2: Calculate total lag

   Total lag = 5 + 0 = 5 messages behind.

3. Final Answer:

   5 -> Option B

4. Quick Check:

   Total lag = sum of partition lags = 5 [OK]

Hint: Add lag values from all partitions for total lag [OK]

Common Mistakes:

• Using LOG-END-OFFSET as lag
• Confusing CURRENT-OFFSET with lag
• Adding offsets instead of lag values

4. You run kafka-consumer-groups.sh --describe --group my-group but see no lag column. What is the likely cause?

medium

A. The Kafka broker is down

B. The topic does not exist

C. The command syntax is incorrect

D. The consumer group has no committed offsets yet

Solution

1. Step 1: Understand missing lag column reason

   If the consumer group has no committed offsets, lag cannot be calculated and may not show.

2. Step 2: Exclude other causes

   Broker down or wrong syntax usually cause errors, not missing lag column; topic existence affects consumption but not lag display here.

3. Final Answer:

   The consumer group has no committed offsets yet -> Option D

4. Quick Check:

   No committed offsets = no lag shown [OK]

Hint: No committed offsets means lag won't appear [OK]

Common Mistakes:

• Assuming broker down causes missing lag column
• Thinking syntax error causes missing lag column
• Confusing topic existence with lag display

5. You notice high consumer lag for a group processing a topic with 3 partitions. The lag per partition is 100, 0, and 50 respectively. What is the best approach to reduce lag quickly?

hard

A. Delete and recreate the consumer group

B. Increase the topic partition count to 10

C. Add more consumers to the group to increase parallel processing

D. Restart the Kafka broker to clear lag

Solution

1. Step 1: Analyze lag distribution

   Partitions have uneven lag: 100, 0, 50. Some partitions are behind.

2. Step 2: Choose action to reduce lag

   Adding consumers can help process partitions faster by parallel consumption.

3. Step 3: Evaluate other options

   Increasing partitions alone won't reduce lag immediately; restarting broker or deleting group won't fix lag directly.

4. Final Answer:

   Add more consumers to the group to increase parallel processing -> Option C

5. Quick Check:

   More consumers = faster lag reduction [OK]

Hint: Add consumers to process partitions faster [OK]

Common Mistakes:

• Thinking restarting broker clears lag
• Believing increasing partitions instantly reduces lag
• Deleting group removes offsets but not lag solution