Did so. The proposal looks perfectly sensible on first reading.
I understand that the patches in
https://issues.apache.org/jira/browse/KAFKA-657 are already in the trunk and
scheduled for 0.8.1? Are they going out with 0.8? If not, what's ETA for 0.8.1?
Either way, I'm going to try my hand at
Yes, it looks spot on.
Thanks,
rob
-Original Message-
From: Alex Zuzin [mailto:carna...@gmail.com]
Sent: Monday, May 20, 2013 11:37 AM
To: users@kafka.apache.org
Subject: Re: Update: RE: are commitOffsets botched to zookeeper?
Did so. The proposal looks perfectly sensible
afaik you dont 'have' to store the consumed offsets in zk right, this is
only automatic with some of the clients?
why not store them in a data store that can write at the rate that you
require?
On Fri, May 17, 2013 at 2:15 PM, Withers, Robert robert.with...@dish.comwrote:
Update from our OPS
to clarify, I meant that Robert could/should store the offsets in a faster
store not that kafka should default to that :)
Thanks Neha
On Fri, May 17, 2013 at 2:22 PM, Neha Narkhede neha.narkh...@gmail.comwrote:
There is no particular need for storing the offsets in zookeeper. In fact
with
