I tested the new patch out and am seeing comparable CPU usage to the
previous patch. As far as I can see, heap usage is also comparable between
the two patches, though I will say that both look significantly better than
0.8.1.1 (~250MB vs. ~1GB).
I'll report back if any new issues come up as I
Thank you Todd for your detailed explanation. Currently I export all
metrics to graphite using the reporter configuration. is there a way I can
do similar thing with offset checker?
On Mon, Feb 16, 2015 at 4:21 PM, Todd Palino tpal...@gmail.com wrote:
The reason for this is the mechanic by
The reason for this is the mechanic by which each of the lags are
calculated. MaxLag (and the FetcherLagMetric) are calculated by the
consumer itself using the difference between the offset it knows it is at,
and the offset that the broker has as the end of the partition. The offset
checker,
Hello,
We've an issue on our Kafka production. (Kafka 0.8.1.1 on 9 Debian Wheezy
servers).
We tried to move a topic from a server to another, but no data was created
on the target.
After some tries when decidec to stop Kafka on this server (kafka3),
removed all topic's data on /var/lib/kafka/*
