Hi team,
I was trying to migrate my consumer offset from kafka to zookeeper.
Here is the original settings of my consumer
props.put(offsets.storage, kafka);
props.put(dual.commit.enabled, false);
Here is the steps
1. set dual.commit.enabled=true
2. restart my consumer and monitor offset lag
That is weird. Are you by any chance running an older version of the
offset checker? Is this straightforward to reproduce?
On Fri, Feb 13, 2015 at 09:57:31AM +0800, tao xiao wrote:
Joel,
No, the metric was not increasing. It was 0 all the time.
On Fri, Feb 13, 2015 at 12:18 AM, Joel Koshy
This is a serious issue, we'll take a look.
-Jay
On Thu, Feb 12, 2015 at 3:19 PM, Solon Gordon so...@knewton.com wrote:
I saw a very similar jump in CPU usage when I tried upgrading from 0.8.1.1
to 0.8.2.0 today in a test environment. The Kafka cluster there is two
m1.larges handling 2,000
Thanks for the explanation. It there a way that I can wipe out the offset
stored in kafka so that the checker can continue to work again?
On Fri, Feb 13, 2015 at 1:31 PM, Jiangjie Qin j...@linkedin.com.invalid
wrote:
I think this is the offset checker bug.
The offset checker will
1. first
So it's not possible to have 1 topic with 1 partition and many consumers of
that topic?
My intention is to have a topic with many consumers, but each consumer
needs to be able to have access to all the messages in that topic.
On 11 February 2015 at 20:42, Zijing Guo alter...@yahoo.com.invalid
Gary,
That is certainly a valid use case. What Zijing was saying is that you can
only have 1 consumer per consumer application per partition.
I think that what it boils down to is how you want your information grouped
inside your timeframes. For example, if you want to have everything for a
I'm going to go a bit in reverse for your questions. We built a restful API
to push data to so that we could submit things from multiple sources that
aren't necessarily things that our team would maintain, as well as validate
that data before we send it off to a topic.
As for consumers... we
