Hi all,
I'm working on implementing a lua kafka client [1], but I'm getting
confused: what does `RequestTimedOut` exactly mean.
At first, from The Kafka Protocal [2], I thought producer should retry when
received `RequestTimedOut`.
But later, I found sometimes the messages may have `commited` as
This means the write occurred on the leader but the followers couldn't
acknowledge in the time bound specified by the user. The write will likely
complete but is not guaranteed to (the leader could immediately crash after
the response is sent). So if you retry you will potentially (likely) have
dup
Hi Yonghui,
I have tried a few ways with different retention strategies to try and
reproduce this issue, but haven't been able to do it. Since it looks
like you can consistently reproduce this, would you able to share a
sample reproducible application (maybe as a github repo) for this issue?
Thanks for your quick reply and clear explanation :)
2015-01-31 22:29 GMT+08:00 Jay Kreps :
> This means the write occurred on the leader but the followers couldn't
> acknowledge in the time bound specified by the user. The write will likely
> complete but is not guaranteed to (the leader could i
Hello,
I ran my own tests made with kafka_2.10-0.8.1.1.tgz binaries with our
application:
1st test:
==
replace all kafka .jar files in our application on consumming side
(without recompiling anything)
=> tests passed, OK
2nd test:
===
replace all kafka .jar files in our applicati
Hello,
I have read Broker.scala source code, and I found the answer:
- With Kafka 0.8.1.1 we used Broker.getConnectionString() in our Java code.
- With Kafka 0.8.2.0, this method has been replaced by a 0-arity method
without the "get" prefix, so we have to change our Java code to call
Broker.con
Hi, Alex,
Thanks for testing RC3.
Broker.connectionString() is actually not part of the public api for the
producer. Is there a particular reason that you need to use this api?
Thanks,
Jun
On Sat, Jan 31, 2015 at 1:53 PM, Alex The Rocker
wrote:
> Hello,
>
> I have read Broker.scala source co
+1 (binding). Verified quickstart and unit tests.
Thanks,
Jun
On Wed, Jan 28, 2015 at 11:22 PM, Jun Rao wrote:
> This is the third candidate for release of Apache Kafka 0.8.2.0.
>
> Release Notes for the 0.8.2.0 release
>
> https://people.apache.org/~junrao/kafka-0.8.2.0-candidate3/RELEASE_NOT
