Hello,
Normally I know that each consumer group has a current offset for each
partition it consumes, and when we delete a group, its current offsets are
deleted with it, and when we (re)create the consumer group again, it will
have no current offsets (meaning it will go from offset 0 or offset late
Hi, what is suggested way to emit lag into Prometheus? Is there a Kafka
Streams job for it? Is Burrow or Kafka Lag Exporter?
Emitting lag from the consumer is not a great option of course, so looking
at independent jobs that emit lag.
Do you know any? Thank you
Hi guys, in case of KTable with KTable joins, is co-location a requirement?
Do the 2 topics need to have the same number of partitions?
https://forum.confluent.io/t/ktable-ktable-joins-is-colocation-needed/1034
Thank you,
Nicolae
