Hi Steve,
You can try to reduce the metadata.fetch.timeout.ms config value, which
will controll how much the send() call can be blocked upon broker metadata
not available (due to broker itself not available).
Guozhang
On Tue, Sep 9, 2014 at 7:00 PM, Tarzia wrote:
> Thanks Guozhang,
>
> Another
Thanks Guozhang,
Another case I am seeing is that producer.send() seems to block when the
brokers are unavailable. This is not the behavior I want (I would rather have
it throw an exception immediately so I can queue the messages for replay). I
will try to confirm this tomorrow.
-Steve
On
Hi Steve:
1. the new producer will be included in the 0.8.2 release for production
usage.
2. The error you reported has been changed as a WARN in the latest trunk.
We realize this should not really be an error case. In general, any errors
will be propagated to the producer in the following two way
Hello,
I am trying to use the new org.apache.kafka.clients.producer.KafkaProducer to
take advantage of error reporting that is lacking in the current "stable" Scala
client (import kafka.javaapi.producer.Producer). Two questions:
* I know that 0.8.2 is not yet released but is the new Producer
