Grokking Kafka and Event-Driven Architecture
Vote

0% completed

​

Diagnosing Consumer Lag

At 14:05 the fraud team's time-lag alert fires: one partition of card-transactions is minutes behind. The engineer on call runs kafka-consumer-groups.sh --describe, repairs what it shows, and runs it again later. The sample program for this page reproduces both looks against a real Kafka 4.4 broker, with 200 transactions per partition instead of millions. It runs one scorer instance per partition, assigned by hand so that the output repeats exactly.

Output:

-- first look: 200 transactions written to each partition

.....

.....

.....

Like the course? Get enrolled and start learning!

Reading Progress

0%

Vote for new content