app
→ events · 0/s · acks=all
No keys (sticky)
sent 0 · acked 0 · failed 0
Three brokers, two topics, two consumer groups, all running right here. Take a guided scenario, or break things yourself: stop a broker, cut its power, add a consumer, drag the timeline back to see it again, or type kafka-topics --describe in the terminal.
Step 1 of 5
This cluster behaves like Kafka before 0.11. Broker 1 leads, broker 2 follows. The producer sends m1 with acks=all.
Based on KIP-101 (Apache Kafka)
→ events · 0/s · acks=all
No keys (sticky)
sent 0 · acked 0 · failed 0
Running
Running
No consumer groups yet.
Click a record to follow its journey.
00000000000000000000.log0 records0 B.index .timeindexown HW 0
00000000000000000000.log0 records0 B.index .timeindexHW: consumers read below this line · LEO: next offset to write · only in the page cache · differs from the leader at the same offset
The concepts behind what you see above. They also live under Notes, tagged #kafka.