Consumer lag monitoring in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is consumer lag in Kafka?

Consumer lag is the difference between the latest message offset in a Kafka partition and the offset of the last message processed by a consumer. It shows how far behind the consumer is.

beginner

Why is monitoring consumer lag important?

Monitoring consumer lag helps ensure consumers are processing messages in a timely manner. High lag means delays or problems in processing, which can cause stale data or system issues.

beginner

Name a common tool used to monitor Kafka consumer lag.

Kafka's built-in tool 'kafka-consumer-groups.sh' is commonly used to check consumer lag by showing current offsets and lag per consumer group.

intermediate

How can you check consumer lag using kafka-consumer-groups.sh?

Run: kafka-consumer-groups.sh --bootstrap-server <broker> --describe --group . It shows partition offsets, current consumer offsets, and lag.

beginner

What does a lag of zero mean for a Kafka consumer?

A lag of zero means the consumer has processed all available messages and is up to date with the latest data in the partition.

What does consumer lag measure in Kafka?

A Number of partitions in a topic

B Number of consumers in a group

C Size of Kafka topic

D Difference between latest message offset and consumer's last processed offset

Consumer lag measures how far behind a consumer is by comparing the latest offset with the consumer's last processed offset.

Which Kafka tool helps you check consumer lag?

A kafka-consumer-groups.sh

B kafka-topics.sh

C kafka-producer-perf-test.sh

D kafka-configs.sh

The kafka-consumer-groups.sh tool shows consumer group offsets and lag.

What does a high consumer lag indicate?

A Consumer is processing messages slowly or stuck

B Consumer is up to date

C Topic has no messages

D Consumer group has too many members

High lag means the consumer is behind and not processing messages fast enough.

Which command option shows detailed consumer group info including lag?

A --list

B --delete

C --describe

D --help

The --describe option shows detailed info including lag for consumer groups.

If consumer lag is zero, what does it mean?

A Topic is empty

B Consumer is caught up with all messages

C Consumer is offline

D Consumer group is new

Zero lag means the consumer has processed all messages and is current.

Explain what consumer lag is and why it matters in Kafka.

Think about how far behind a consumer is and what happens if it falls behind.

Describe how to check consumer lag using Kafka command-line tools.

Focus on the command and what information it shows.

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