Florin,
In a high-level consumer "ConsumerConnector" you can setup the property
auto.commit.enable = false. Then you can call commitOffsets after
processing the message.
Calling commitOffsets after every message will slow processing down
dramatically. So setup a timer or other coordination mechan
Thanks Jay, this is helpful information. Controlling when offsets are committed
is possible only with the SimpleConsumer, correct? I believe that the
ConsumerConnector (the high level consumer) commits the offsets automatically.
It would be nice to have a hook into it that I can override to let
I think there may be some confusion as we significantly strengthened the
guarantees in the latest release (0.8) and since this is pretty recent we
haven't updated all the documentation. Prior to this we did not support
replication.
As of 0.8:
1. If your replication factor is 3 you can tolerate 2 f
Disclaimer: I only have experience right now with 0.7.2
On Sun, Jul 7, 2013 at 11:35 AM, David James wrote:
> Sorry for the long email, but I've tried to keep it organized, at least.
>
> "Kafka has a modern cluster-centric design that offers strong
> durability and fault-tolerance guarantees." an
Sorry for the long email, but I've tried to keep it organized, at least.
"Kafka has a modern cluster-centric design that offers strong
durability and fault-tolerance guarantees." and "Messages are
persisted on disk and replicated within the cluster to prevent data
loss." according to http://kafka.
