Hi kiran,
I would check the log end offset of the in-sync partition first, and check
the lags of the offsets with the leader offset. (You can check by metric:
`kafka.log:type=Log,name=LogEndOffset,topic=xxx, partition=xx`)
Then, I would check if the follower is doing fetching without error by
chec
Hi,
We are running a Kafka cluster in Kubernetes. We have a use case where we are
trying to dynamically remove advertised listeners from a side car container if
our Kafka cluster loses heartbeat with our other application service. And
ofcourse add if the heartbeat is ever a success.
I tried usin
Hi Fares,
You're right in your description of the contents of the __consumer_offsets
topic, and how they are stored.
The most common reason for an uneven load on the consumer offsets are.
1. Configuration of offset commits in the client
2. Load on topic being consumed
If a topic has 10 partition