Hi Kafka'ers,
I am trying to get the Mirrormaker working with two separate clusters, one
as the source and the other as the target. The topic I'm trying to copy
over exists on both the source and target clusters. Here are the relevant
entries in my consumer and producer properties files, which I'
Alex,
Are you sure you have data continually being sent to the topic in source
cluster after you bring up MM? By default auto.offset.reset=largest in MM
consumer config which means MM only fetches the largest offset if the
consumer group has no initial offset in zookeeper.
You can have MM print m
Hi All,
I am having a Kafka Storm Topology which is ingesting events published to
Kafka and processing on top of that data.
Although apart from some latency I found that everything was going good.
But recently I came across a issue which I couldn't get any solution yet.
I publishing some events
Solon, Mathias,
Thanks for testing this out. I just uploaded a slightly modified patch in
https://issues.apache.org/jira/browse/KAFKA-1952. The new patch may not
improve the latency and CPU usage further, but will potentially improve
memory consumption. It would be great if you guys can test the n
Hi,
Is there a way to get the current partition number and current offset, when
using the *high level consumer* in 0.8.2?
I went through the previous messages and in the previous version I think there
are none.
The reason we want to do this, is that I plan to have a consumer without the
You can get the partition number and offset of the message by
MessageAndMetadata.partition() and MessageAndMetadata.offset().
To your scenario you can turn off auto commit auto.commit.enable=false and
then commit by yourself after finishing message consumption.
On Mon, Feb 16, 2015 at 1:40 PM, Ar
