I'm checking into this on our side. The version we're working on jumping to
right now is not the 0.8.2 release version, but it is significantly ahead
of 0.8.1.1. We've got it deployed on one cluster and I'm making sure it's
balanced right now before I take a look at all the metrics. I'll fill in
There are FetcherLagMetrics that you can take a look at. However, it
is probably easiest to just monitor MaxLag as that reports the maximum
of all the lag metrics.
On Fri, Feb 13, 2015 at 05:03:28PM +0800, tao xiao wrote:
Hi team,
Is there a metric that shows the consumer lag of a particular
We can reproduce this issue, have a theory as to the cause, and are working
on a fix. Here is the ticket to track it:
https://issues.apache.org/jira/browse/KAFKA-1952
I would recommend people hold off on 0.8.2 upgrades until we have a handle
on this.
-Jay
On Fri, Feb 13, 2015 at 1:47 PM, Solon
As Manikumar mentioned the code in 0.8.2 is not released and that class is
just a stub (it doesn't do anything yet). If you would like to try out the
new consumer you can try it on trunk. However be aware that it doesn't yet
do partition balancing among topics as that is pending server side work.
Hey all,
We found an issue in 0.8.2 that can lead to high CPU usage on brokers with
lots of partitions. We are working on a fix for this. You can track
progress here:
https://issues.apache.org/jira/browse/KAFKA-1952
I would recommend holding off on upgrading to 0.8.2 until we have a fix for
this
Paul,
There is ongoing work to move to Kafka API instead of making
calls to zookeeper.
Here is the JIRA https://issues.apache.org/jira/browse/STORM-650 .
-Harsha
On Fri, Feb 13, 2015, at 01:02 PM, Paul Mackles wrote:
I noticed that the standard Kafka storm spout gets topic
Hello,
I recently upgraded a java producer from the 0.8.2-beta client library to
the 0.8.2. The producer is writing to a 0.8.1.1 kafka cluster. It was
running without issues with the 0.8.2-beta version, but when i switched to
the new one i get snappy exceptions on kafka logs.
Logs:
Thanks for the fast response. I did a quick test and initial results look
promising. When I swapped in the patched version, CPU usage dropped from
~150% to ~65%. Still a bit higher than what I see with 0.8.1.1 but much
more reasonable.
I'll do more testing on Monday but wanted to get you some
